Skip to main content
ION’s prebuilt integrations and automations live in the ION Marketplace. To deploy one, open the Marketplace, configure its connection to ION, and fill in the fields the integration needs.

​
Deploy from the Marketplace

  1. In the sidebar, select Integrations to open the ION Marketplace.
  2. Find the integration or automation you want, then select Configure.
  3. In the ION API connection step, enter your ION API key and secret, then select the environment to run in. See API keys for how to create them.
  4. Fill in any additional fields the integration requires. These point the integration at the ION objects or attributes it acts on, and come as free-text inputs or pick-lists. Each integration documents its own fields.
  5. For a partner integration, connect the external system (such as Arena, Duro, or Smartsheet) using that partner’s setup steps.
API keys are environment-specific. A sandbox key and secret do not work in production. Use keys generated in the same environment you are deploying to.
An API key inherits the permissions of its creator. Create the key as a user with the permissions the integration needs.
The integration’s webhook subscriptions are created when you first deploy an instance, and are removed only when you deactivate that instance, not when you pause it.
Some webhook-driven automations need their trigger set explicitly: a ResourceEnum value (what to listen to) and a WebhookSubscriptionActions value (what to listen for). Find the valid values in ION’s GraphQL documentation explorer, and match the input format exactly as it appears there.

​
Troubleshooting

​
You don’t see the Integrations page

Your organization might not have Marketplace access yet. Contact Support to request it.

​
An automation stops triggering after an environment change

Each environment needs its own API keys, so an instance moved between sandbox and production stops working. Redeploy it with keys from the target environment:
  1. Record the current setup of your instances.
  2. Deactivate the existing instances to clear any stray webhook subscriptions between environments.
  3. Create new instances using the API key and secret for the correct environment.
  4. Confirm the trigger’s resource and action when you create each instance.

​
A deployed integration shows no executions, and webhook events return 401

The integration deployed successfully, but you see no executions, and the webhook events in the ION API return 401 errors. This happens when API keys were entered into the trigger details. Open the integration’s summary page, select Reconfigure, and expand the trigger details. Delete any API key listed there with the trash icon. The trigger details should have nothing below the URL for each flow.
  • API keys for creating the credentials an integration uses
  • Webhooks for how ION delivers events to an integration