/ Docs
Vendor Integrations

AWeber

Last updated October 13, 2025 · View as Markdown

Aweber_logo.svg AWeber is an online all-in-one marketing platform specializing in email marketing. It helps organizations communicate more effectively and profitably with prospects and customers.

In order to integrate AWeber with Relyance AI you will need a Client ID and Client Secret.

In AWeber:

  1. Login to your AWeber account.
  2. Go here: https://labs.aweber.com/apps
  3. Click the Create A New App button.
  4. Fill out the form with the following values: Application Name: Provide a meaningful name (e.g. Relyance Scan) Author: Provide a name Application Website: https://www.relyance.ai Callback URL: https://root.relyance.ai/api/oauth2 Client Type: Confidential OAuth Redirect URL: https://root.relyance.ai/api/oauth2 Description: Provide a meaningful description
  5. Once filled out click the Create New App button.
  6. This will return you to the My Apps page. Find your app and copy the Client ID and Client Secret to be used in Relyance.

AWeber-3.png

AWeber-4.png

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 Vendors and Data Stores filter.
  5. Find the AWeber integration card and click it to open its connections.
  6. Under Authentication Method, choose Oauth2 / App Token.
  7. Paste the Client ID and Client Secret into their respective fields.

AWeber-1.png

  1. Click Authenticate.
  2. This will bring you to AWeber page to authorize your integration. Login and click Allow Access.

AWeber-5.png

  1. At this point, you should see the following result on the Vendor Integrations page:

AWeber-2.png

  1. Congratulations, you are now connected to AWeber.

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. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
  2. A credential rotated at the vendor is not picked up here. Client Secret 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.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example aweber/<connection_id>) or reading it with the relyance_integration_connection data source.

← Previous
Avalara