How to use these recipes

These are task-level patterns, not parameter schemas. Open each linked node reference for exact fields, allowed values, branches, variables, and JSON. Build in a draft, publish explicitly, and activate only after human review.

1. Follow up on a Facebook lead

Suggested path:

1. Facebook Lead Received trigger for the intended connected form.
2. Add Contact Tag action and/or Move to Pipeline Status action.
3. Wait action when follow-up must resume during business hours.
4. Send SMS action or Send Email action.
5. Create Task action for a human owner.

The Facebook Page/form, publication, active state, Contact context, reusable template, communication endpoint, consent, suppression, and provider readiness must all pass.

2. Route form submissions by Contact data

Suggested path:

1. Form Submission trigger.
2. If / Else action using Contact conditions.
3. In the matching branch, add tags, move Pipeline status, send an internal notification, or create a task.
4. In the other branch, add the alternate operational path.

If/Else ends its parent path. Both outcomes must be built inside the exact if and else branches; do not place a sibling action after it.

3. Create a service-visit reminder

Start with Service Job Created, Service Job Updated, or a Repeat Every trigger, depending on the business rule. Add a Wait that resumes at the intended date/window before the communication action.

Automation Send SMS and Send Email do not automatically consult Scheduling Hours. An explicit Wait with business-hours constraints is required when timing matters. The later send still rechecks Contact eligibility and provider readiness.

4. Wait for a reply with a timeout

Use the Wait action in reply mode, select SMS, email, or any supported reply channel, and enable a timeout when the process needs an escape path.

• Put the success path inside continued.
• Put the no-reply path inside timeout.
• A resumed run starts inside one branch and does not rejoin the original parent path.

Reply waits require a Contact context. A disabled Automation permanently cancels unresolved published waits; enabling it later does not resume them.

5. Notify an internal owner before contacting a customer

Use Send Notification for an in-app/user notification, then a Wait or communication action only when the workflow requires it. Web push visibility depends on the recipient's device registration; the stored notification remains available in the Notifications page even when an OS banner is not shown.

6. Connect a User to a Contact call

Use the task guide Use Call Connect in an Automation, then consult the Call Connect node reference for the exact active schema. Provider callbacks determine the final call evidence; do not treat the internal User answering as proof that the Contact connected.

Safety checklist before activation

• Trigger and resources point to the intended tenant objects.
• Draft is published and the intended publication is active.
• Communication recipients are eligible and consented.
• Waits make timing explicit.
• Branches contain every follow-up action.
• Provider-dependent actions have current channels/integrations.
• A human has reviewed external messages, calls, webhooks, and record mutations.

Related guides

• Build, Publish, and Monitor Automations
• Troubleshoot Automations
• Troubleshoot Message Delivery