New
Starting from a Ready-to-Use Scenario
Creating a workflow from scratch requires knowledge of triggers, actions, and their settings. The scenario catalog spares you from this: each scenario is a complete workflow, named, described, and connected, which only needs to be created, reviewed, and then activated.
Where to Find It
In the Automation hub, click on New Workflow. The Existing Scenario mode is offered first. Choose a category, then a level, and the scenario that matches your needs.
A scenario already has its name and description: nothing to enter. Once created, it opens in the visual editor, deactivated. You review, adjust, and then activate.
Seven Categories
| Category | What it Covers |
|---|---|
| Prospecting & Sales | New contacts and companies, forms turned into opportunities, follow-ups |
| Marketing & Forms | Acknowledgments, nurturing, wallet cards, scheduled reports |
| Social Media | Comments, thanks, scheduled posts, moderation |
| Appointments & Events | Confirmations, reminders, appointment preparation, sessions |
| Customer Service & Emails | Received emails, emergencies, follow-ups from the client area |
| Files & Custom Objects | Files created from a form, deadlines, status tracking, imports |
| Integrations & Webhooks | Incoming webhooks, external API calls, monitoring, summaries |
Three Levels
- Simple: one trigger, one or two actions. It runs immediately.
- Advanced: conditions, branches, delays, or loops. The scenario adapts to each case: an urgent email is not treated like others, a paid appointment triggers a verification.
- Agentic: AI reads, writes, or decides within the framework you set. It qualifies a request, drafts a response, classifies a comment, and the scenario directs the next steps according to its verdict.
Settings That Remain to Be Chosen
Some settings depend on your account and cannot be guessed: the pipeline and its stage, the target custom object, the social account for posting, the wallet card template, the sender of an email.
The scenario indicates these with a "settings to choose" badge even before creation. In the editor, open the relevant node and choose the value from the list. As long as a mandatory setting is missing, the corresponding action fails, and the execution clearly states this on the Executions page.
Customize Without Breaking
A scenario is a starting point, not a constraint. You can:
- change texts (subject, body, message) and insert variables like
{{email}}or{{first_name}}; - add a node, remove one, move a delay;
- duplicate a branch to cover an additional case.
The only safeguard: keep a single trigger at the head of the scenario.