Build your first Replify automation

Open Automations to create or edit a workflow. You need permission to manage workspace automations.

Build and activate

1. Name the draft. Click Add trigger at the top of the canvas, choose an event and narrow its conditions. A scheduler runs on its own and replaces other triggers.
2. Click a canvas + where you want to add a node, including inside a branch. The menu groups Messages, CRM actions, Logic and Webhook under colored headings. A selected node uses its group color for its border.
3. Select a node to edit it in the settings panel. Content contains its options. Use the footer trash button to immediately remove the selected node and its child paths from the draft. Advanced also provides move/delete controls. Copy and paste paths from the canvas controls.
4. For messages, select the sender and write the text. Open the Insert variable dropdown and choose a value to insert at the cursor. Use Include media and Interactive replies toggles for optional content. The preview uses example variable values and sends nothing.
5. Choose Review & activate. Use Save draft to keep it inactive, or Save & activate to validate and enable it. To pause an active automation, open Review changes, turn off Active after saving, and save inactive.
6. Before using it broadly, check matching, non-matching and duplicate events, response ownership, reply waits, external failures and human-owned conversations. Open Automation settings → Execution logs to inspect saved runs.

Drag empty canvas space with the left mouse button to pan without changing zoom. Nodes, menus and native scrollbars keep their usual controls; touch scrolling stays available. On smaller screens, selecting a node opens its settings; close the panel to return to the canvas. Zoom controls affect the canvas only.

Save and recover drafts

• Inactive automation drafts auto save after a short pause when Automation settings → Auto save inactive drafts is on. Active automations and library templates need a reviewed manual save.
• All changes saved confirms the current version was saved to the workspace. Changes pending save, Saving… and Save failed describe different states; a browser copy is not a confirmed workspace save.
• Browser recovery is best effort and scoped to your workspace and member. It remains available when auto save is off, but clearing browser storage removes it.
• If a local draft differs from a saved workflow, choose Restore or Discard. Restoring pauses auto save until you review and save the changes.
• Workspace changed means another save won. Reload the workspace version, then review the retained local copy before saving again.
• Save not confirmed after creating a draft can mean the server saved it before the connection failed. Check the Automations list before retrying. If you choose Discard browser copy, saved automations remain in the workspace.

Message actions and response ownership

• To add a reply button or list option, write its label first and press Enter or Add. Up to 3 reply buttons (20 characters each) or 10 list options (24 characters each). Set the reply timeout and configure the reply/Timeout paths on the canvas.
• Media supports choosing/replacing/removing a file, with a 25 MB upload limit and any stricter provider limits. Turning media off removes the attachment. With interactive content, media is sent first as a separate message.
• Removing replies, changing their type or turning them off asks for confirmation if configured path actions would be removed. Those affected actions are removed from the draft, never silently moved into another reply path. Adding the first reply moves following steps into its path; review the canvas before activation.
• Send Message supports reply buttons, lists and a website button. A website button opens an HTTP/HTTPS link and continues without waiting for a reply.
• Message, contact and lead variables use the current workspace. An explicit WhatsApp sender must own the conversation; templates must be approved for that sender. The default uses the conversation sender and retains supported multi-channel behavior.
• Sending, assigning or claiming the response can own the turn. Silent tagging and record updates do not block AI in automation-first mode.
• DND blocks outgoing messages while incoming messages still arrive. A suppressed send skips its path and creates no reply wait. Turning DND off does not replay it.
• If a send or external call fails, inspect its execution log and arrange human follow-up. Reconcile an uncertain result before retrying.

Other node options

• Send Template: choose an approved template and review its full text. Optional Flow settings and reply timeouts appear only when relevant. Changing the sender or template, or disabling a timeout, asks before removing populated reply paths.
• Assign / Create deal / Update field: choose a teammate or record first. A deal's stage depends on its pipeline; changing a field clears its old draft value. Tags and DND apply to the current contact.
• Wait: choose the wait type, then its values. Check frequency and retry limits are under the expandable advanced section when relevant. Drip shows batch size and delay with their limits.
• Condition / Route by trigger: configure the branches on the canvas. Choose a source before adding a trigger route. Removing populated routes/conditions requires confirmation.
• Go To: choose a message or branch destination; unavailable targets need replacement. Webhook: enter its POST endpoint and JSON body. Toggle custom headers on, enter a name/value and add it; duplicate names are flagged.

Priority and Assistant

Automation settings → Advanced → Response priority orders matching automations: lower numbers run first, equal priorities run oldest first. Default: 100. It does not speed up delivery.

The embedded AI Workflow Builder is removed. Use the header AI Assistant to request a supported automation draft, then review it under the existing permissions and approvals. It does not bypass activation or sending rules.

Give each active workflow an owner and review date. Archive obsolete workflows.