Flows FAQ

Yes! Click Start from template on the Flows page to browse templates organized by category: Sales, CX, Marketing, Analytics, Docs, Productivity, and Email. Templates give you a fully configured flow that you can customize further. You can also save your own flows as templates to share with your team. Learn more about templates.

Yes. Every change to a flow is tracked in version history. Click the action menu and select History to see all previous versions. You can view the changes made in each version and restore any previous version with one click. The restore is also recorded in history, so you'll always have a complete audit trail.

Yes! Click Create with AI on the Flows page and describe what you want your flow to do in plain English. The AI will generate a complete flow with triggers, conditions, and actions. You can also modify existing flows with AI by clicking the magic wand icon and describing the changes you want to make. All AI changes are shown for review before being applied. Learn more about AI-powered flows.

Flows have four statuses: Draft (the flow is saved but not active - it won't trigger on any events), Active (the flow is published and running - it will trigger on matching events), Paused (temporarily stopped, can be resumed), and Archived (hidden from the main list but preserved with all history). You can change status from the flow detail page.

Flows can operate on six resource types: Customer (app events, subscriptions, usage), Ticket (helpdesk workflows), Deal (sales pipeline), Contact (CRM contacts), Affiliate (partner programs), and Organization (scheduled organization-level operations). Each resource type has its own set of available triggers, conditions, and actions. Choose the resource type when creating a new flow.

There's no hard limit on the number of flows you can create. Most users run dozens of flows without any issues. However, if you're planning to create an exceptionally large number of flows or very complex flows with many entry points, it's worth reaching out to our team first - we can help optimize your setup for the best performance.

Flows run completely automatically once published. When the trigger event happens and any conditions are met, the flow executes its actions without any manual intervention.

Yes! Use the flow debugger to test your flow against a specific customer, ticket, or other resource before publishing. You can run in dry run mode to simulate the flow without actually executing actions - no emails sent, no tags changed, no webhooks called. Open it from the action menu in the flow editor or on the flow detail page. Learn more about testing and debugging flows.

All flows with matching triggers will run independently. For example, if you have two flows that both trigger on "customer installs app", both will execute when someone installs your app.

Yes! If your flow has multiple entry points (different triggers), a customer can go through all of them without any special settings. Each entry point works independently. However, if you want a customer to re-trigger the same entry point multiple times, you need to enable "Allow customers to re-enter this flow" in your flow settings.

Yes, you can unpublish a flow at any time to stop it from running. Your flow will remain saved and you can republish it whenever you're ready.

Check these common issues:
• Make sure your flow is published
• Verify the trigger event is actually happening (check your app's activity)
• Review any conditions - they might be too restrictive
• For usage event triggers, ensure the events are being sent correctly to Mantle
• Check if the customer meets all the specified conditions

Yes! You can add multiple conditions to make your flows more specific. All conditions must be met for the flow to run. For example, you could trigger on "customer installs app" AND "customer has tag 'VIP'" AND "customer is not on trial".

Yes! You can use the Scheduled trigger type to run flows on a set schedule - one-time, daily, weekly, or monthly. Scheduled flows run against all matching resources (filtered by segment, tags, status, etc.) when the schedule fires. You can also add time delays between steps in any flow. Learn more about scheduling flows.

Yes, flows will trigger for test customers unless you specifically add a condition to exclude them. You can add "Test customer is false" as a condition to prevent flows from running on test accounts.

No, email actions require valid customer email addresses. If you haven't set up email collection yet, check out our email setup guide to learn how to import customer emails or set up automatic collection through Mantle Email.

Check the flow activity log to see exactly what happened. For email actions specifically, common issues include:
• Customer has no email address
• Email template has errors or missing content
• Email isn't configured to send to the right contact list
• Issues in the email editor (broken links, missing images, etc.)

Other common failures:
• Slack actions failed because integration isn't properly configured
• HTTP requests failed due to incorrect URLs or authentication

The activity log will show you the specific error for each failed action.

Yes! Each flow has an activity log that shows every time it's triggered, which actions succeeded or failed, and any error messages. This is great for debugging and monitoring your automations.

Add more specific conditions to narrow down when the flow runs. You can also use custom fields to track flow states - for example, set a field when the flow runs and add a condition to check if it's already been set.

Yes, you can edit published flows at any time. Changes take effect immediately. Every change is tracked in version history, so you can always see what was changed and restore a previous version if needed. You can also use AI to describe changes in natural language - just click the magic wand icon and describe what you want to modify.

The flow will run each time the trigger event happens, unless you've added conditions to prevent it. For example, if your flow triggers on "customer installs app" and they uninstall/reinstall, the flow will run again on the second install.