Workflows

Workflows let your company design multi-step automations on a visual canvas. Each workflow defines how data enters the process, which steps run, and what happens when conditions match. Save a workflow to publish a version you can test before turning it on for live runs.

Who can use Workflows

Role	Access
Admin	Create, edit, save, test, delete, and enable workflows
Staff	View workflows and inspect runs in read-only mode
Member	No access to the Workflows area

Eric follows the same rules as the signed-in user. Only admins can change workflows through Eric or the product editor.

Getting started

Open Workflows from the main navigation to see your company’s workflow list. Admins can create a workflow from the list and open it on the canvas editor.

The list shows each workflow’s title, whether it is enabled, and its latest saved version. Admins can delete a workflow from the list; that action cannot be undone.

Author on the canvas

The editor is built around a canvas that shows triggers, steps, and the connections between them.

Triggers start live runs when a workflow is enabled:

• Schedule trigger — runs on a recurring schedule you define in the workflow’s timezone.
• Data-change trigger — runs when a configured Dataset or Query Dataset row newly matches your predicate. Optionally, also runs on later refreshes when configured watched fields change while the row still matches.

Steps shape what happens after a run starts:

• Starting input — declares the typed fields a manual or triggered run supplies.
• Condition — routes the run through the first matching branch, with a final Else path for everything else.
• Eric routing — lets Eric choose one declared route from mapped upstream data.
• Transform Data — reshapes an object or each item in a list using field mappings before a later step uses it.
• Wait — pauses the run until a duration elapses or the next matching calendar time.
• Create Report — generates a durable Report PDF from a Report Blueprint for a later delivery step.
• Email — sends email when a live run reaches the step.
• HTTP Request — calls an HTTP API when a live run reaches the step.
• Download File — downloads a file from a connected API for later steps in the same run.
• Upload File — sends a file downloaded earlier in the run to another connected API.
• Link Records — enrolls an existing pair of linked records for bidirectional scalar field updates.
• Sync Records — compares mapped fields on an enrolled pair and updates each connected system when values differ.

Transform Data steps

A Transform Data step maps fields from an earlier step’s output into a new object or list of objects. Use it when you need to reshape records—for example, turning CRM line items into the structure an HTTP Request expects—without fetching data or calling an API.

Open the step inspector to choose whether you are transforming a single object or every object in an array, select the source output, and define output fields. Mapped results are available to later steps as transformed data. Defaults can fill missing or null values; invalid conversions fail the step and stop downstream actions.

Use Preview with sample data to check a mapping against sample JSON without running other steps or creating a workflow run.

HTTP Request steps

An HTTP Request step calls an external API when a live run reaches it. Open the step inspector to configure the method, URL, authentication, headers, and JSON body.

Choose No authentication for public https:// URLs. To call a vendor API with stored credentials, select a saved integration connection or saved credential (Bearer token, basic authentication, or API key header). Integration connections use the same accounts connected under Settings → Integrations; you do not need a Dataset to use a connection in a workflow. Connect or reconnect an account from the inspector when needed. The provider checks access when the request runs.

With a connection selected, enter a path relative to that connection’s API base. Without authentication, enter the full public URL. Map upstream values into path placeholders and query parameters. For On HTTP error, choose Fail this step or Continue with response when a later Condition should branch on the response status or body.

Download File and Upload File steps

A Download File step fetches binary content from a connected API when a live run reaches it. Configure the URL, authentication, and optional filename the same way as an HTTP Request step. Later steps receive a file reference; temporary storage is removed after the run completes successfully, or after seven days if the run fails or is cancelled.

An Upload File step sends a file reference from an earlier Download File step to a connected API. Choose the HTTP method, destination path, and binary or multipart upload format. Map upstream values into path placeholders and query parameters the same way as HTTP Request steps.

Each file transfer is limited to 25 MB and 120 seconds per HTTP request. Use Download File and Upload File together to move attachments between systems—for example, after a Salesforce Files row triggers the workflow.

Link Records and Sync Records steps

Use Link Records and Sync Records together to keep mapped scalar fields aligned between two existing records in connected systems—for example, phone and website on a Salesforce Account and a NetSuite customer that already reference each other.

Link Records enrolls a one-to-one pair and declares which text, number, and boolean fields sync between the left and right integration connection. Choose a Conflict winner (left or right) for fields both systems change differently since the last synchronized value; that side’s value is copied to the other, including clearing a value. Link Records does not create records or send field updates on its own.

Sync Records runs the comparison for an enrolled pair. Independent changes on each side are merged. Matching values produce no writes, which prevents update loops. Run history shows which fields changed and, when conflicts were resolved, which side won.

Configure record IDs and field mappings in YAML from the step inspector. Each mapping supports up to 50 scalar fields. Use integration connections the same way as HTTP Request steps.

For ongoing updates, pair Sync Records with a Data-change trigger on a Dataset or Query Dataset that joins the two record IDs. Add watchFields for the source columns you want to react to; the trigger also runs when those values change after a refresh while the row still matches your condition.

Select a trigger or step to open its inspector. Admins edit configuration there and return to the canvas when finished. Unsaved canvas changes stay in the editor until you save the workflow.

Saving validates the workflow and publishes a new version when the compiled definition changes. Fix any validation errors shown at the top of the editor before saving again.

Use the Enabled switch when a workflow is ready for live admission from its triggers. Disabled workflows can still be edited and tested.

Test before going live

Admins can run a test from the editor. The test saves unsaved changes first, then runs against the latest saved version.

By default, a test evaluates conditions and routing without sending email, making HTTP requests, downloading or uploading files, linking or synchronizing records, or generating reports. Turn on Run live actions when you need the test to perform those steps; it still runs as a test and ignores the Enabled switch.

Provide Starting input values that match the fields you declared on the workflow. The test results explain which path the run took and which actions were skipped.

Inspect Workflow Runs

Open Runs from the editor to review recent test and live runs. Each run keeps the version it started with, even if you later edit or disable the workflow. Failed runs and runs with unknown delivery stay visible so an admin can decide what to do next. Runs that fail starting-input validation show which fields did not match. HTTP Request and Upload File steps include response details in the timeline; full response payloads are retained for 30 days. Link Records and Sync Records steps report whether records were linked or synchronized and which conflict fields were resolved.

Eric on the canvas

Admins can open the Eric panel on the workflow canvas for help while authoring. Eric can suggest and apply changes to the same workflow files the editor saves. If Eric saves while you still have local edits, reload to pick up Eric’s version or keep working from your draft.