Create your first automation

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 a role that can manage Automations. For an Agent message action, first prepare:

• one enabled agent;
• one connected Slack workspace;
• one enabled Slack channel bound to that same agent.

Build the definition

1. Open https://automations.infra.one/your-organization-slug.
2. Select New automation.
3. Enter an Automation name that describes the outcome, not only the event.
4. Under Trigger, choose a trigger type and fill its options.
5. Under Conditions, select Add condition only when the trigger alone is too broad.
6. Under Action, choose the action and complete every required field.
7. Select Create automation.

For a signed external event, choose Incoming webhook. For a generated Slack message, choose Agent message.

Save one-time webhook credentials

When the trigger is Incoming webhook, creation also creates an endpoint. The success state 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

1. Open the saved Automation.
2. In Test delivery, enter a representative JSON object.
3. Select Start test delivery.
4. Confirm the form shows Accepted.
5. In Run history, wait for the webhook-delivery row and action row to reach a successful state.
6. 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.