Automations overview
Understand how Infra One turns Contacts, application, Forms, Dealflow, opportunity, investment, and signed-webhook events into durable actions.
An Automation connects one Trigger to one configured Action, optionally guarded by Conditions. It is organization-scoped, can be enabled or disabled independently, and records its work in Run history.
Use Automations when a repeatable event should produce a repeatable outcome without relying on a person to notice and relay it.
The execution model
- A product event or signed incoming webhook creates the trigger data.
- Conditions decide whether the event is in scope.
- The action validates its stored configuration against current organization state.
- Durable work runs outside the browser.
- Run history records status, time, error category, external result, and any safety instruction.
The available trigger and action choices depend on your organization, role, and enabled product surfaces.
Trigger families
The current editor can react to:
- Contacts: Contact created, Contact updated, Added to group, and Removed from group;
- Applications and Forms: Application status changed and Form submitted;
- Dealflow: Deal created and Deal stage changed;
- Opportunities: Opportunity created, Opportunity stage changed, and Opportunity closed;
- Investments: Investment signed and Investment executed;
- External systems: Incoming webhook, using a signed JSON object.
Some choices appear only when the related product or administrative access is available. Internal Ori proposals do not create customer Automations; create and review the definition on the Automations surface itself.
Available outcomes
The current editor lists Sync to group, Remove from group, Update contact, Create deal, Move opportunity card, and Agent message, and configures one action per Automation. Update contact and Move opportunity card currently lack required controls in that editor; review Triggers, conditions, and actions before choosing an action.
Automation states
Enabled means matching events may execute the action. Disabled keeps the definition and history but does not process normal trigger events.
New incoming-webhook Automations start disabled. This is intentional: creation also produces a live endpoint and a one-time signing secret, so you can store credentials, send a test delivery, and review the result before enabling production traffic.
The production release-announcement definition: one signed webhook, one agent task, one bound Slack channel, and payload-derived wrappers.
Why delivery is durable
External senders can retry, workers can restart, and Slack can time out after accepting a post. Infra One uses an idempotency key and a persisted delivery lifecycle to avoid treating an HTTP response as the whole story.
The important distinction is:
- Accepted means Infra One validated and stored the request.
- Succeeded means generation and the external post completed.
- Failed before post can be retried safely after the cause is resolved.
- Failed after claim requires inspecting Slack before any manual retry, because delivery may have happened.