- Documentation
- User Application
- Templates
- Integrations
Webhook connector
תוכן זה אינו זמין עדיין בשפה שלך.
A Webhook connector links one of the project’s webhooks to the template. Cellosign then calls the webhook for this template’s transactions, at the stage of the connector.
Webhooks you can select
Section titled “Webhooks you can select”The Reference list shows the project’s webhooks that suit the stage:
| Stage | Webhooks | Settings |
|---|---|---|
| PRESET | Post notification when a new session created in workflow | None |
| LIVE | Get data from remote source | Triggers and Field Mapping |
| LIVE | Post notification when client logged in to form, Post notification when form loaded on client browser | None |
| SUBMIT | Post business process result (Archive), Post notification when form is submitted, Post notification when session is expired, Post notification when session is deleted | None |
Only webhooks without Use implicit are listed. Webhooks with Use implicit run for every template, and they appear in the connectors list as IMPLICIT. See Implicit connectors.
Add a Webhook connector
Section titled “Add a Webhook connector”- On the Integrations tab, click Connectors, and then click the Add button of the stage.
- In Source, select Webhook. In Reference, select the webhook.
- For a “Get data from remote source” webhook, set the trigger and the field mapping. See below.
- Click Save, and then save the template.
Get data from remote source
Section titled “Get data from remote source”With a “Get data from remote source” webhook in the LIVE stage, Cellosign sends field values to a remote service while the recipient fills in the form, and fills fields with the values in the answer. See Field change for the request and the answer.
Triggers
Section titled “Triggers”Select when the webhook is called. See Triggers. A Trigger Field is required.
Field Mapping
Section titled “Field Mapping”Outgoing (Request) maps form fields to the names under which their values are sent. Click Add Mapping for each field:
| Setting | What to enter |
|---|---|
| Form Field | The field whose value is sent. Each field can be used in one row only. Required in each row. |
| Alias | The name under which the value is sent. If you leave it empty, the field ID is used. |
Incoming (Response) maps the values in the answer to form fields:
- With Use Response Mapping off (the default), a value in the answer fills the field that has the same ID.
- With Use Response Mapping on, a value is matched by its alias first, and then by field ID. Click Add Mapping for each value:
| Setting | What to enter |
|---|---|
| Alias | The name of the value in the answer. |
| Form Control | The field to fill with the value. |
To fill several fields with the same value, add a row for each field with the same alias. Each field can be used in one row only. If the response mapping of another connector also fills the field, the warning “This field is also targeted by another connector’s response mapping” appears. You can still save.
When Use Response Mapping is on, add at least one row, and fill in both Alias and Form Control in every row. Turning it off removes the rows.