Create your first automation
Create a trigger-action definition, test it through the same durable path used in production, and enable it after checking the result.
This guide creates an Automation and establishes a safe rollout sequence. The exact fields beneath Trigger and Action change with the types you select.
Before you begin
You need access to the organization on automations.infra.one and the manage_contacts capability used for Automation mutations. Only the Agent message action requires these additional prerequisites:
- one enabled agent;
- one connected Slack workspace;
- one enabled Slack channel bound to that same agent.
Build the definition
- Open
https://automations.infra.one/your-organization-slug. - Select New automation.
- Enter an Automation name that describes the outcome, not only the event.
- Under Trigger, choose a trigger type and fill its options.
- Under Conditions, select Add condition only when the trigger alone is too broad.
- Under Action, choose the action and complete every required field.
- Select Create automation.
For a signed external event, choose Incoming webhook. For a generated Slack message, choose Agent message.
The current editor saves one Action with each Automation. Create a separate Automation when the same trigger must produce a second independent action.
Do not choose Update contact or Move opportunity card for a new definition: those choices are visible, but the current editor does not collect configuration required by their executors. Use one of the other four actions until the controls are repaired.
Save one-time webhook credentials
Incoming-webhook Automations start disabled. Creation also creates an endpoint and shows:
- Endpoint URL
- Signing secret
Copy both immediately into the sender’s secret store. The signing secret is shown once and cannot be recovered. Select I saved the secret only after the destination contains the copied value.
If you lose it, use Rotate secret on the Automation page and update the sender before enabling traffic.
Test the durable path
- Open the saved Automation.
- In Test delivery, enter a representative JSON object.
- Select Start test delivery.
- Confirm the form shows Accepted.
- In Run history, wait for the webhook-delivery row and action row to reach a successful state.
- Inspect the external result. For Slack, open the destination and verify one message prefixed with
[Test delivery].
The test uses the same webhook and worker path as production. It may execute while the Automation is disabled, which lets you validate safely.
Enable production execution
Use the Enabled toggle only after the test result is correct. Then send one real event with a fresh idempotency key and verify the final external result again.
Success check
The Automation header shows Enabled. Run history shows one successful webhook delivery and one successful action for the real event. The destination contains exactly one expected result.
Troubleshooting
- If a trigger or action is missing, confirm that the related product is enabled for the organization and that your access permits it.
- If Create automation is unavailable, select a name, Trigger, and Action, then complete every field shown for those choices.
- If a webhook test succeeds while normal events do not run, confirm the Automation is Enabled and its Conditions match the event.
For detailed recovery, see Troubleshoot automations.