Integrations - ION Manual
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
An integration is a script that runs when something happens in ION. An ION event triggers it, usually through a webhook and sometimes on a schedule. From there it can do almost anything: read and write ION data through the GraphQL API, call an external system, send a notification, or generate a document. First Resonance builds and ships prebuilt integrations through the ION Marketplace, and you can also build your own. Integrations take many shapes. Two common ones:
- A third-party integration syncs data between ION and another system, such as pulling part releases from your PLM or pushing purchase orders to your ERP.
- An ION automation runs logic against ION itself, such as querying and mutating data through the GraphQL API when an event fires.
Getting started
- Deploy a prebuilt integration or automation: browse the ION Marketplace and the catalogs below, then follow Deploy an integration or automation.
- Build your own: if nothing prebuilt fits, use the Workflow Builder, webhooks, or the GraphQL API. See Create an integration.
- Design the data flow across systems: see the ERP and PLM reference architecture.
- Generate PDFs from ION objects such as purchase orders and run packets: see Export data as PDF.
Partner integrations evolve quickly. Your Manufacturing Success Engineer has the current state of every connector and what’s in the pipeline.
Third-party integrations
Connectors First Resonance and its partners maintain for the systems you already run. Most use standard protocols ( AMQP for messaging, GraphQL for direct queries, and webhooks), so you don’t wire each one from scratch.
PLM and PDM
Arena
Pull part and BOM releases from Arena PLM into ION.
Duro
Sync the Duro catalog with ION parts and BOMs.
Teamcenter
Siemens Teamcenter PLM integration.
Solidworks
Direct CAD release into ION.
ERP and finance
NetSuite
Inventory, purchase order, and receipt sync with NetSuite ERP.
QuickBooks
Sync purchase order details to QuickBooks Online.
Ramp
Spend data and procurement context.
Procurement and sourcing
Cofactr
Component sourcing and supply chain data.
Procurable
Strategic sourcing and supplier management.
Datum
Supplier data and component intelligence.
Silkline
Supply chain intelligence.
Collaboration and productivity
Slack
Notifications and slash-command lookups.
Smartsheet
Two-way sync with Smartsheet plans.
ION automations
Prebuilt ION automations that First Resonance maintains. They run logic against ION when an event fires, and can write back to ION, send notifications, generate documents, or call an external system. Deploy them from the Marketplace.
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.
Auto-assign issue on creation
Assign new issues to a role or team.
Auto-checkout of run steps
Check out run steps when their requirements are met.
Auto-consumption of lineside inventory
Consume non-serial-tracked inventory automatically.
Auto-populate PO line attributes
Propagate attributes from a purchase order to its lines.
Auto-approve part-procedure relationships
Approve part-procedure links automatically.
Automatically send purchases to suppliers
Email approved purchase orders to suppliers.
Imprint attributes from one object to another
Copy attributes between objects on an event.
Kit packing pick-list PDF
Generate a pick-list PDF for a kit.
Purchase order PDF and versions
Generate purchase order PDFs.
Prevent run closure if aBOM is not completed
Block run closure until the aBOM is complete.
Set close-by run step on issue creation
Set an issue’s resolve-by run step on creation.