Iterable

​

What’s supported

​

Supported actions

This connector supports:

• Read Actions, including full historic backfill. Please note that incremental read is not supported, a full read of the Iterable instance will be done for each scheduled read.
• Write Actions.
• Proxy Actions, using the base URL https://api.iterable.com.

The Iterable connector supports writing to and reading from the following objects:

• campaigns
• catalogs
• lists
• webhooks

Iterable allows the following objects to only be read, and not written to:

• channels
• jobs
• journeys
• messageTypes
• messages
• metadata
• templates

Iterable allows the following objects to only be written to:

• templatesEmail
• templatesInApp
• templatesPush
• templatesSMS
• users

​

Example integration

For an example manifest file of an Iterable integration, visit our samples repo on Github.

​

Using the connector

This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.)

To start integrating with Iterable:

• Create a manifest file like the example above.
• Deploy it using the amp CLI.
• Embed the InstallIntegration UI component. The UI component will prompt the customer for an API key.
• Start making Proxy Calls, and Ampersand will automatically attach the API key supplied by the customer. Please note that this connector’s base URL is https://api.iterable.com.

​

Creating an API key for Iterable

Click here for more information about generating an API key for Iterable. The UI components will display this link, so that your users can successfully create API keys.