> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firstresonance.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Create an integration

> Build your own integration when no prebuilt connector fits, using the Workflow Builder, webhooks, or the GraphQL API.

When no [prebuilt connector or automation](/automate-with-ion/integrations) fits, you can build your own. Three patterns work well, from least to most code.

## Workflow Builder

Build an integration visually in ION, without code. Use it to connect a system that isn't on the prebuilt list, or to assemble a custom automation from triggers and actions. See [Accessing the Workflow Builder](/automate-with-ion/integrations/workflow-builder/accessing-the-workflow-builder) to get started, then [Create a flow](/automate-with-ion/integrations/workflow-builder/creating-a-flow) to wire up its trigger and ION connection.

The Workflow Builder is available to selected organizations. Contact [Support](https://support.firstresonance.io/) to enable it.

## Webhooks

Push ION events to your own system as they happen. Subscribe to the resources and actions you care about, and ION delivers an event to your endpoint when they occur. Use this when your system reacts to changes in ION. See [Webhooks](/api-reference/guides/webhooks).

## GraphQL API

Read from or write to ION directly. The same GraphQL surface that powers the ION interface is available to you, so anything the app can do, your integration can do. Use this for two-way sync, bulk operations, or anything the Workflow Builder and webhooks don't cover. New to the API? Start with [Getting started](/api-reference/getting-started). To take an API integration from your first call to production, see [Build a production integration](/api-reference/guides/build-a-production-integration). For the full surface, see [the API reference](/api-reference).

<Tip>
  Connect the highest-leverage system first, usually your ERP, since inventory and purchase order data drive the most downstream value. Pick one source of truth per concept (parts in PLM, inventory in ION, the general ledger in ERP) and sync one way from there rather than bidirectionally syncing every field.
</Tip>

## Related

* [Deploy an integration or automation](/automate-with-ion/integrations/deploying-integrations-and-automations)
* [ERP and PLM reference architecture](/automate-with-ion/integrations/erp-plm-reference-architecture)
* [Webhooks](/api-reference/guides/webhooks)
* [API reference](/api-reference)