Overview
"Custom HTTP" is a reusable connected service that can be used for authentication to third party services.
Configuration
Open Site Configuration 🠖 Connections 🠖 Connected Services.
Add new "Custom HTTP" service from the available service types to start the configuration process.
"Account Configuration" 
Parameter | Description |
|---|---|
Service Name | Descriptive name of the integration service. The name will be displayed in the configuration of “Send to connected service” action |
Account | You can select from existing accounts or leave “Create new…” to create the new one on this step |
Account Name | Descriptive name of the connected account |
Authorization Type | Used for specifying the type of authorization for integration with 3rd party service
|
Server URL | URL of service you want to connect |
Timeout | Time during which system is trying to get a response from 3rd party service. If the time elapsed and no response received, the timeout message will be shown |
Timeout Message | A message to be displayed if 3rd party service is not available during the specified timeout |
Header Name | Name of HTTP request header containing auth data (i.e."Authorization", "X-API-KEY" etc) |
Header Value | Value sent in HTTP request header for authentication to 3rd party service.(i.e Basic Auth, API key etc) |
"Service Configuration"
User | A user must be specified in order to work with security mechanism during webhook call from third-party service. Having regular active user with any access right is enough. "API User" mode is not required. |
Linked App | Application used for bi-directional integration. Should be created and configured beforehand |
Please note:
"User" and "Linked App" parameters needed only if bi-directional integration is configured.
Once connected service is saved - webhook url (based on Api key from saved service) gets displayed.
