Configure integration
The “Configure” screen (or “Settings”, if the integration already exists) opens the form for a specific integration. Here you paste the credentials the other service gives you and check that the connection works before activating it. The “Integrations” link at the top goes back to the catalogue.
1. Current status
When the integration is already saved, the “Current Status” block shows whether it is “Active”, in “Error”, “Testing...”, “Not Configured” or “Disabled”, and its “Last Verified” date. An “Error” usually means the credentials have expired or are wrong: reconfigure it.
2. Basic configuration and credentials
Under “Basic Configuration” enter the “Integration Name” and choose the “Environment”: “Production”, “Sandbox” or “Development”. Then under “Credentials” paste the data the other service provides (API keys, secrets, tokens, webhook URLs); each field explains below where it comes from. A secret that is already saved shows as “Configured”: leave it as it is to keep it, or type a new one to replace it. In “User provisioning (SCIM 2.0)”, “Generate token” creates the token you paste into your identity provider; it is shown once.
3. Save, authorise and test
Press “Save Configuration”. Once saved, “Test Connection” appears: if the result is correct the integration becomes “Active”; if it fails, check the credentials. Some integrations (DocuSign, Google, SharePoint) first ask you to “Authorise” in a pop-up window. In Telegram, “Register webhook” lets notifications be linked to each user's account. “Cancel” leaves without saving.
4. Documentation and next step
“View Documentation” opens the step-by-step guide for that integration. WhatsApp and Telegram have their own guides, with each platform's requirements. On the messaging ones, at the bottom, “Go to notification preferences” leads to where each user switches the channel on: configuring the integration sends nothing until then.