These recipes answer the practical questions already appearing in search: tagging contacts by source, logging selected activity, creating tasks after replies, sending opt-in email sequences, moving paid opportunities and booking appointments from online pages.
Every reliable automation has five parts: a precise trigger, filters, data updates, actions and stop conditions. Build the smallest version first, test it with a named record, then add branches only when the business process requires them.
Examples include first response under ten minutes, every reply owned, paid deals moved to onboarding or every booking confirmed.
Use the actual form, reply, payment, appointment or call event instead of a broad contact update whenever possible.
Filter by source, campaign, consent, product, status, channel, business hours or pipeline so only intended contacts continue.
Apply the source tag, owner, task, opportunity or stage that records what the workflow is doing.
Deliver the approved message, notification or booking path after the CRM state is correct.
Stop nurture when a person replies, books or pays. Test the happy path and failure path, then review execution logs and conversion outcomes.
Trigger
A source-specific form, ad, inbound webhook or campaign event
Actions
Result
Teams can segment, route and report without overwriting original acquisition history.
Trigger
Customer Replied with selected channel, phrase or intent filters
Actions
Result
Every meaningful reply has a visible owner and response deadline.
Trigger
Form Submitted, tag added or external opt-in event
Actions
Result
The sequence starts from a documented opt-in and respects contact behavior.
Trigger
Payment Received with Success status and product filters
Actions
Result
Payment becomes a verified operational handoff.
Trigger
Customer completes a supported booking calendar
Actions
Result
The appointment and CRM context remain connected from booking to outcome.
Trigger
Missed inbound call matching the intended number and status
Actions
Result
A missed call receives a fast, governed response while a person owns the follow-up.
Confirm it is published, the test record met the exact trigger and filters, and the connected channel delivered the event.
Review re-entry, duplicate events, wait branches and stop conditions. Use an event ID or sent-status field for actions that must run once.
Put assignment before task creation and test empty owner, unavailable owner and territory conflicts.
Filter by payment status, product and source, then match the correct contact and opportunity before updating the stage.
Connectors, events, actions and usage charges can vary by plan, account and region. Verify the options shown in your account and test them before publishing.
Trigger from the source-specific event, normalize the source name, preserve first source, update latest source separately and apply a consistent tag for routing and reporting.
Use Customer Replied with channel or intent filters, assign the conversation, create a task with a due time, notify the owner and stop conflicting nurture steps.
Use Payment Received filtered to successful status and the intended product or payment source, then create or update the matching opportunity and move it to the paid or onboarding stage.
Use the native Form Submitted trigger for Lead Connector forms or the supported external-form trigger, inbound webhook or connector for another form provider.
Connect the event to an owner, next action and outcome, then test it before launch.
Discuss your integration.png){kind=logo}