Front

Front is a SaaS platform that provides businesses a way to collaborate, comment and assign shared inbox emails. Its collaboration software allows companies to communicate with customers.

In order to integrate Front with Relyance AI you will need an API Token.

In Front:

1. Login to your Front account.
2. Click on the gear icon in the top right-hand corner.
3. Select Plugins & API from the left-hand navigation menu.
4. Click API on this page to bring up the API page.
5. Click the New Token button to create a 3rd party developer token.
6. Provide a meaningful name and select Shared Resources as the scope.
7. Click the create button to create the token.
8. Click on your newly created token and copy the Token key to be used in Relyance AI.

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 FrontApp integration card and click it to open its connections.
6. Under Authentication Method, choose Custom.
7. Paste the API Token into its respective field.

The Authentication step asks for:

• API Token: required; held as a secret.

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 Front.

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 Shared resources. 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 Token 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" "frontapp" {
  vendor = "frontapp"
  name   = "<your connection name>"

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

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