iContact

iContact is an online email automation and marketing solution that allows you to easily create and track a professional and effective email campaign. It offers email design, list management, campaign management and social media publishing.

In order to integrate iContact with Relyance AI you will need an API Application ID, API Username, API Password, Account ID, and Client Folder ID.

In iContact:

1. Login to your iContact account.
2. Click on the account menu in the top right-hand side and select and select Settings and Billing.
3. Click on iContact Integrations in the settings list.
4. Click the Create button next to Custom API Integrations.
5. FIll in the Custom API form with the following values:

API Name: << Provide a relevant name e.g. Relyance AI >> API Description: << Provide a description >>

6. Click Save Changes.
7. Copy the API Application ID, API Username, and API Password from the Getting Connected section on this page. Also copy the Account ID and Client Folder ID from the the Account Information section below. These values will be used in Relyance ID.

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 iContact integration card and click it to open its connections.
6. Under Authentication Method, choose Custom.
7. Paste the API Application ID, API Username, API Password, Account ID, and Client Folder ID values into their respective fields.

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

11. Congratulations, you are now connected to iContact.

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 credential rotated at the vendor is not picked up here. API Password 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.
2. Check the address fields before suspecting the credentials. Account ID identifies which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

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" "icontact" {
  vendor = "icontact"
  name   = "<your connection name>"

  auth = {
    method = "api-credentials"
    params = {
      api_app_id = "<api_app_id>"
      api_user = "<api_user>"
      account_id = "<account_id>"
      folder_id = "<folder_id>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_pwd = var.icontact_api_pwd
    }
    secrets_wo_version = 1
  }

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