Connections
A connection is where a Webhook, Slack or Teams channel delivers to: a URL with its authentication. You set a connection up once, in the Integrations app under Connections, and reuse it in as many notification targets (and data exports) as you want.
Create a connection
Open the Integrations app, go to Connections and press Add connection. Pick the kind:
Webhook
Any HTTPS endpoint: your own service, a Power Automate flow, a Logic App.
| Field | Description |
|---|---|
| Name | A name for the connection |
| URL | The endpoint Capture will call. Notifications require HTTPS. |
| Method | POST (the default), PUT or PATCH |
| Authentication | How Capture proves itself to your endpoint (see below) |
| Custom headers | Extra headers added to every call |
| Metadata headers | Adds a timestamp header to every call |
| Retry header | Adds a header that counts the retries of a delivery |
For the authentication you can choose:
| Type | What you fill in | What Capture sends |
|---|---|---|
| None | nothing | nothing |
| API key | a key | an X-API-Key header |
| Bearer | a token | an Authorization: Bearer header |
| Basic | a username and password | an Authorization: Basic header |
| Custom | your own header names and values | those headers |
Slack
Paste the incoming-webhook URL of your Slack channel. In Slack you get one by adding the Incoming Webhooks app to the channel.
Teams
Paste the webhook URL of your Teams workflow. In Teams you create one with the Post to a channel when a webhook request is received workflow template.
How secrets are handled
- The authentication values (the API key, token, password or custom header values) are stored encrypted and can never be read back, not even by you. You can only replace them.
- The URL and the custom headers of a webhook connection can be read back by anyone who may view connections. So keep secrets in the authentication fields, never in the URL or in a custom header.
- A Slack or Teams URL is itself the secret. It is stored encrypted, and the page only shows its host.
After adding the connection to a target, use the channel's Send test button to check the setup end to end. See Targets.
Good to know
- A connection cannot be deleted while a notification target still uses it. Remove it from those targets first.
- The same connection can also be used by data exports. For exports an HTTP URL is accepted, but a notification target only works with HTTPS.