Workflows & automations

Go to Craftor → Workflows to create automations triggered by a form submission (or other events). Each workflow has a trigger and one or more ordered steps; any step can have its own condition (only run if X) and a "Continue on error" toggle so one failed step doesn't stop the rest.

Building your first workflow

1. 1Craftor → Workflows → Add New, then give it a name — this is for your own reference only, visitors never see it.
2. 2Pick a trigger (see below) and, for Form Submitted or Payment Succeeded, the specific form it applies to.
3. 3Click Add Step and choose an action — see the full catalog below.
4. 4Fill in that action's fields, using {field_name} merge tags anywhere you see "Use {field_name}" in a field's help text — the insert-bar next to those fields lists every field on the selected form so you don't have to remember the exact auto-generated name.
5. 5Optionally add a condition to the step (only run if a field matches a rule) and toggle Continue on Error if a later step shouldn't be skipped when this one fails.
6. 6Add more steps for more actions — they run in order, top to bottom, all from the same trigger.
7. 7Save. The workflow is live immediately and doesn't need anything enabled on the form widget itself — Form Submitted fires for every future submission of the selected form.

Triggers

• Form Submitted — a visitor submits any form.
• Payment Succeeded — a Payment field's charge is confirmed.
• Entry Updated — an admin saves an edit on the "Edit Entry" screen, Craftor → Entries.
• Entry Deleted — an admin deletes an entry, from the single "Delete" row action or a bulk delete.

Entry Updated and Entry Deleted also expose who took the action: use {actor_name}, {actor_email}, {actor_ip}, and {action_time} in any step's text fields — a Send Email step with the message "Entry deleted by {actor_name} ({actor_email}) from {actor_ip} at {action_time}" is a common one for keeping a team notified of destructive changes. These tags only appear in the merge-tag insert bar (and only resolve to anything) on those two triggers — a public Form Submitted trigger has no logged-in "actor" to report.

CRM & marketing

• Mailchimp
• ActiveCampaign
• HubSpot
• Pipedrive
• Airtable

Google Workspace

• Google Sheets
• Google Drive (file uploads)
• Google Calendar (create an event)

Messaging

• Slack
• Discord
• Twilio (SMS)

WordPress & site

• Send Email, HTTP Webhook
• Create Post / Page, Update Entry Status
• Register User, Update User, Log In User, Send Password Reset

Store each service's API key or OAuth connection once, under Craftor → Settings → Connections — every workflow step, on every form, reuses it. A single submission can trigger several actions in sequence, e.g. adding a HubSpot contact, appending a Google Sheets row, and posting to Slack from the same entry.