Use the New/Updated Record trigger to monitor specific signing events in OneSpan Sign. When a transaction reaches a selected status, such as Transaction completed, the trigger can update downstream systems, including your CRM or workflow applications.
Prerequisites
Before using this trigger, you must configure event notifications in your OneSpan Sign account.
Configure the callback URL: In your OneSpan Sign account, set the Callback URL to the URL provided by this trigger.
Set up callback authentication: Select an Authentication method in OneSpan Sign to secure incoming callbacks. In the trigger, choose the same method and provide the required credentials.
Subscribe to events: In OneSpan Sign, choose the Events you want to monitor. In the trigger, select the corresponding event that will start the recipe.
To monitor multiple events, create a separate recipe for each event. All recipes will share the same callback URL.
Input
Input field | Description |
|---|---|
Event name to listen for | Select the OneSpan Sign event that should start this recipe (for example, Transaction completed). |
Callback authentication | Choose how to secure incoming callbacks:
|
Callback Secret | If using BASIC authentication, enter the same callback secret configured in your OneSpan Sign account. |
Output
Output field | Description |
|---|---|
Callback Payload | Returns the complete OneSpan Sign callback payload for the selected event, including event type, package ID, and timestamp information. For a full description of all payload fields for each event type, see Setting Up Callback Notifications. |
OAuth2 Access Token | If OAUTH2 authentication is selected, the trigger returns the OAuth 2.0 access token included in the callback request so the recipe can validate or reuse it. |
HTTP Headers | All other HTTP headers sent in the callback request are included in the output so your recipe can inspect or use them. |