Skip to main content
A workflow is a saved automation that runs on its own every time a trigger condition is met. You build it by describing what you want to the Atmet agent in chat, and the platform converts your instructions into a deterministic process that executes reliably in the background. Once active, a workflow runs without you lifting a finger — and you can always review, edit, or pause it at any time.

​
How workflows are built

Every workflow goes through two phases: Builder phase — You chat with the agent to describe the trigger, the steps, and the expected outcome. The agent asks clarifying questions, previews the logic, and confirms the design with you before saving anything. Any actions that are outward-facing or destructive — such as sending emails or deleting records — require your explicit sign-off during this phase before the workflow is activated. Runtime phase — Once you activate the workflow, it runs deterministically on every qualifying event. The agent no longer improvises; it follows the exact steps you confirmed in the builder phase.
The runtime engine is separate from the conversational agent. This means your workflows execute consistently and predictably, independent of how the agent might interpret a similar request in a new chat.

​
Creating a workflow

1

Open a new chat

Navigate to New Chat in the sidebar. You’ll build the workflow through a guided conversation with the agent.
2

Describe the automation

Tell the agent what you want to automate. Include the trigger (what starts it), the actions (what it should do), and any conditions (when it should or shouldn’t run). For example: “When a new row is added to my Google Sheet, create a contact in HubSpot and send a welcome email via Gmail.”
3

Answer the agent's clarifying questions

The agent will ask for any missing details — which account to use, what the email subject should be, whether it should send automatically or wait for your go-ahead. Answer directly in chat or fill in the inline form it renders.
4

Review the workflow summary

The agent presents a plain-language summary of the workflow logic before saving. Check that the trigger, conditions, and actions match your intent.
5

Confirm and activate the workflow

For any outward-facing or destructive action — such as sending an email or deleting a record — the agent will describe exactly what it plans to do and ask for your one-time sign-off. Once you confirm, the workflow is activated and immediately begins watching for its trigger.

​
Triggers

A trigger is the event that starts a workflow. Atmet supports three trigger types:

Event-based triggers

The workflow fires when something happens in a connected app — a new email arrives in Gmail, a deal is updated in HubSpot, or a message is posted in Slack.

Scheduled triggers

The workflow runs on a recurring schedule — hourly, daily, weekly, or on a custom cron expression you define.

Webhook triggers

The workflow fires when an external system sends an HTTP request to a unique URL Atmet provides. Useful for connecting tools not in the native integrations catalog.

Manual triggers

Run a workflow on demand from the Workflows dashboard or by asking the agent to run it in chat.

​
Actions

At each step of a workflow, the agent can perform actions across your connected integrations. Common actions include:
  • Send or reply to a message — Gmail, Slack, Telegram, Discord, or X (Twitter)
  • Create or update a record — HubSpot contacts, Salesforce opportunities, Jira issues, Asana tasks, Notion pages
  • Read or write data — Google Sheets rows, Google Docs content, Google Drive files
  • Post to a calendar — Create or update Google Calendar events
  • Run code — Execute a script or call an external API via webhook
You can chain multiple actions in sequence, add conditional branches (“if the deal value is over $10,000, notify the account manager”), and loop over lists of records.

​
Workflow statuses

Every workflow has a status that reflects its current state:

​
Viewing run history and step logs

To see how a workflow has performed, open the Workflows section in the sidebar and click the workflow name. The Run History tab shows every execution, with timestamps and a pass/fail status for each run. Click into any individual run to see the Step Log — a line-by-line record of what the agent did at each step, including the data it read, the records it created, and any errors it encountered.
If a run shows an error, open its step log and look for the first step marked with a red indicator. The log entry will describe what went wrong — for example, an expired integration token, a missing required field, or a rate-limit response from an external API. Fix the underlying issue, then re-run the workflow from the dashboard or ask the agent to retry it in chat.

​
Pausing, editing, and deleting workflows

To pause a workflow, open it from the Workflows dashboard and toggle the Active switch to off. The workflow stops responding to triggers but retains all its configuration — you can reactivate it at any time. To edit a workflow, open it and click Edit in Chat. This reopens the builder conversation with the full workflow context loaded. Describe what you want to change, and the agent will update the configuration. If any changes introduce outward-facing or destructive actions, it will ask for your sign-off before saving. To delete a workflow, open the three-dot menu on the workflow card and select Delete. Deleted workflows cannot be recovered, but their run history is preserved in your audit log for 90 days.
Editing an active workflow pauses it automatically during the edit session. Remember to reactivate it once you’ve confirmed the changes.

​
Naming and organizing workflows

Clear workflow names save time when you’re managing many automations. Use a naming convention that captures the trigger, the action, and the scope — for example:
  • Gmail → HubSpot: New Lead Intake
  • Weekly: Revenue Summary to Slack
  • Jira: Auto-assign Bugs to Engineering
You can also use the search bar in the Workflows dashboard to filter by name, status, or connected integration.