Waymaker
Automations

Actions

Learn about Actions in WaymakerOS.

ActionsWorkflows

Actions define what an automation does when triggered. Add multiple actions to build multi-step workflows.

Action types

Create table row

Insert a new row into a table.

Configuration:

  • Select the target table
  • Map trigger variables to table columns

Example: When a form is submitted, create a row with {{name}} in the Name column and {{email}} in the Email column.

Send email

Send an email to one or more recipients.

Configuration:

  • To — email addresses (static or from trigger variable like {{email}})
  • Subject — email subject line (supports variables)
  • Body — email content (supports variables and basic HTML)
  • From — your configured sending domain

Update record

Modify an existing row in a table.

Configuration:

  • Select the target table
  • Match condition — how to find the row to update (e.g., where id equals {{record_id}})
  • Fields to update — which columns to change and their new values

Call webhook

Send an HTTP request to an external service.

Configuration:

  • URL — the endpoint to call
  • Method — GET, POST, PUT, DELETE
  • Headers — custom headers (e.g., Authorization)
  • Body — JSON payload (supports trigger variables)

Action sequence

Actions run in order — top to bottom. The result of one action can be used in subsequent actions.

Reordering actions

Drag actions up or down to change the execution order.

Adding delays

Insert a Wait step between actions to add a time delay:

  • Wait 5 minutes, 1 hour, 1 day, etc.
  • Useful for follow-up emails or delayed processing

Conditions on actions

Each action can have a condition that determines whether it runs:

  1. Click the action
  2. Click Add Condition
  3. Set the condition (e.g., {{budget}} > 10000)

If the condition is false, the action is skipped and the automation continues to the next action.

Error handling

If an action fails (e.g., a webhook returns an error), the automation logs the error and continues to the next action. Check the Run History to see which actions succeeded and which failed.

Run history

Every automation execution is logged:

  1. Open the automation
  2. Click Run History
  3. See each run with:
    • Trigger data
    • Action results (success/failure)
    • Error messages
    • Execution time

Next steps