Typeform

Typeform is a web-based platform you can use to create anything from surveys to apps, without needing to write a single line of code. It's used to create all kinds of interactions - from job applications, employee feedback, and creative content marketing, to organizing team events, validating product ideas, and handling customer requests.

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

In Typeform:

1. Login to your Typeform account.
2. Click on the top left-hand workspace icon to get the ORGANIZATION drop-down menu.
3. Click Admin settings.
4. In the left-hand navigation menu, click Developer apps.
5. Click Register a new app.
6. Fill out the form with the following values: App name: Provide a meaningful name (e.g. Relyance Scan) App website: https://www.relyance.ai Redirect URI: https://root.relyance.ai/api/oauth2 Developer email: Use your login account email
7. Click Register app.
8. Copy your Client Secret to be used in Relyance.
9. Click Got it.
10. This will return you to the Developer apps dashboard. Find your app and copy the Client ID 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 Typeform 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.

9. Click Authenticate.
10. This will bring you to the Typeform site to authorize Relyance. Click Accept.

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

12. Congratulations, you are now connected to Typeform.

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 typeform/<connection_id>) or reading it with the relyance_integration_connection data source.