Automate

Create workflows with AI or the editor

Configure triggers, conditions and actions, then verify the outcome.

For app creators | Reviewed

Open this guide as MarkdownDownload all guides

Before you begin

Open Logic & Flow. Identify the triggering table, matching conditions and intended action. Use harmless records and test recipients when verifying messages or data changes.

Build with AI

  1. Open the workflow AI assistant in Logic & Flow.
  2. Describe event, table, conditions and action using real field names.
  3. Review the proposal and warnings, especially recipients, targets and substitutions.
  4. Apply the proposal and save app changes.
  5. Trigger one controlled example and check Workflow Logs and the actual result.

Trigger and action reference

  • Triggers: record creation, update, deletion and scheduled daily evaluation.
  • Conditions include equals, not equals, contains, greater/less than and supported date comparisons.
  • Actions include email, updating/creating records, HTTP requests, fetching records and moving records.
  • Availability and permission checks still apply. An action name is not authority for arbitrary external access.

Example

When a Tasks record is created and Priority equals High, send a test email with the task title to the test recipient I provide. Do not update other records.

Record substitution: {{CURRENT.Title}}

Variables

Use the variable picker where available. {{CURRENT.Field}} refers to the triggering record. Supported lookup paths can follow relationships, but related records must exist and be readable. Verify recipients before sending. Never put credentials into prompts or ordinary record fields.

Check and recover

Verify the saved rule and matching event. Read Workflow Logs and inspect the target record or mailbox separately. An absent log is not proof of success. Check for an existing result before repeating an uncertain send.

Daily evaluation is not an exact-time delivery guarantee. Avoid rules that repeatedly trigger each other. AI allowance does not promise unlimited workflow throughput or email delivery.

Design versus execution

AI drafting consumes shared AI allowance. Running a saved ordinary workflow is separate. There is no general runtime AI writing action. Use Approvals Hub when a change must wait for sign-off.