Iterable

Iterable is a cross-channel marketing platform that powers unified customer experiences and empowers you to create, optimize and measure every interaction across the entire customer journey.

In order to integrate Iterable with Relyance AI you will need an API Key.

In Iterable:

1. Login to your Iterable account.
2. Click on the Integrations dropdown in the top navigation bar. Select API keys.
3. Click on the Create API Key button.
4. This will bring up a dialog to create your new key. Provide a meaningful Name, set the Type to Server-side and click Create.
5. In the resulting dialog, copy the API Key to be used in Relyance.

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Vendor Integration tab.
5. Find the Iterable integration card and click it to open its connections.
6. Under Authentication Method, choose Custom.
7. Paste the API Key into its respective field.

9. Additional Features:
   • Select the Enable Data Inspection checkbox if you wish Relyance also to inspect the data.
   • Click the Enable DSRs checkbox in order to enable this integration in your DSR workflows. For more information on Relyance features, please refer to this help center article: here.

The Authentication step asks for:

• API Key: required; held as a secret.

10. Click Authenticate.
11. At this point, you should see the following result on the Vendor Integrations page:

12. Congratulations, you are now connected to Iterable.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. A feature you enabled returns nothing. Some scopes belong to a feature rather than to the connection: Data subject requests needs Server-side. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. A credential rotated at the vendor is not picked up here. API Key is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

resource "relyance_integration_connection" "iterable" {
  vendor = "iterable"
  name   = "<your connection name>"

  auth = {
    method = "api-key"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_key = var.iterable_api_key
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}