Both ION automations and ION Actions run custom logic on an ION event, but they work differently. An ION Action runs inside ION while a change is being saved, so it can allow, block, or warn on that change. An ION automation runs on the integration platform and reacts to an event that has already happened, so it can’t allow, block, or warn on a change. Instead it takes action, such as firing mutations, sending notifications, or calling external systems.
Integrations
ION automations
The prebuilt ION automations available in the Marketplace, and what each one does.
An ION automation is a prebuilt integration that First Resonance maintains and runs logic against ION when an event fires. It can write back to ION, send notifications, generate documents, or call an external system. Deploy one from the Marketplace; see Deploy an integration or automation.
You can browse this same list in ION itself: in the sidebar, select Integrations.
Some of these automations are also available as a Workflow Builder template: a version you add to your own Workflow Builder and customize yourself, instead of one First Resonance runs for you. The Template available column notes which ones.
Was this page helpful?
⌘I