Reach out to support@logicgate.com or your relationship manager to enable this feature.
Use Risk Cloud webhooks to seamlessly extend your integrations by sending event data from Risk Cloud to external systems in real time. This enables you to automatically detect Risk Cloud events and trigger custom actions across your connected tools.
Webhooks make your integrations more dynamic and responsive. When a specified event occurs in Risk Cloud, a Webhook can send event data to an external URL via an HTTP request—keeping your systems synchronized without manual effort.
You can configure a Risk Cloud Webhook as a type of Job Operation. It can be triggered by any of the following events in your Risk Cloud environment:
- Record Due – fires when a record is approaching or past its due date
- Record Reassigned – fires when a record is manually reassigned
- Record Created – fires when a record is created
- Record Moved – fires when a record is moved to a new step in a workflow
- Fixed Scheduled – fires at a recurring or set time
Setting up Risk Cloud Webhooks can be accomplished in the following steps:
-
Work with your relationship manager or customer success manager to enable Risk Cloud Webhooks in your environment.
NOTE: Risk Cloud Webhooks may need to be added to your Risk Cloud subscription agreement. - Configure the external webhook URLs that you would like to send data to.
- Create jobs in Risk Cloud with your desired triggering event and use the new webhook operation to send data to your specified URL.
Configuring Webhook URLs
Once Risk Cloud Webhooks are enabled in your environment, you can add webhook URLs from the Admin > Integration page. Click the gear icon on the Webhooks integration card and select Configure. A modal will appear where you can add your webhook URLs.
Make sure to give your Webhook URLs recognizable names, as this is how they will be referenced when you create a Job.
Your webhook will be saved and, if URL requires authentication was selected, you will be presented with a one-time secret key. This key is presented only once and can be used to ensure that data is coming from Risk Cloud.
NOTE: You can add and manage multiple Webhook URLs directly from the integration card configuration module in the future, including options to edit, enable, disable, or delete.
Creating a Risk Cloud Webhook Job
Now that you have configured one or more webhook URLs, you can begin adding webhook operations to your Jobs.
Once you have specified your trigger and an optional message, you will want to select the “webhook” operation.
Once this operation is selected, you can specify which webhook URL should be sent data when the job is triggered. We will show you an example of what data is being sent based on the workflow/trigger that you have selected.
NOTE: No custom field data will be sent with Risk Cloud Webhooks. We are only sending event data including job, record, and workflow identification data.
When you save your job everything will be ready for Risk Cloud to start sending event data via webhooks. You can learn more about creating jobs in this help article.
How Risk Cloud Delivers Webhooks
When a job runs a webhook operation, Risk Cloud sends an HTTP POST to your configured URL and waits for your endpoint’s response. That response determines the outcome recorded in Risk Cloud:
| Outcome | What it means |
|---|---|
| Delivered | Your endpoint returned a 2xx HTTP status. Risk Cloud considers the data received. |
| Failed | Your endpoint returned a non-2xx status, or Risk Cloud could not reach it at all. |
If a delivery does not succeed on the first attempt, Risk Cloud automatically retries it several times in quick succession. If every attempt fails, the delivery is recorded as Failed and Risk Cloud sends a failure notification email to the user who created the webhook URL and to your Risk Cloud administrator.
NOTE: A failed delivery does not stop future deliveries. The next time the job is triggered, Risk Cloud will attempt to send the webhook again.
Monitoring Webhooks with the Webhook History Page
Access: The Webhook History page is available to users with the Build or Admin - All entitlement.
The Webhook History page lists webhook operation executions across your environment, newest first, with the outcome of the most recent delivery attempt for each one. Users must have the with the Build entitlement and will only see webhook executions for jobs they're entitled to.
There are two ways to get to the Webhooks History page:
- From Jobs history: Go to Build > Jobs > History and click the Webhook History link in the note above the table. This opens the full, unfiltered list.
- From a specific job: Open the job in the job builder and click View Webhook History on the webhook operation card. This opens the page pre-filtered to that job. From the filtered view, you can click Webhook History in the intro text to return to the full list.
Reading the Table
Each row represents one webhook operation execution and shows the details of its most recent delivery attempt.
| Column | What it shows |
|---|---|
| ID | The job execution operation ID. Use this when searching, or when referencing a specific delivery with LogicGate Support. |
| Webhook | The name of the webhook URL that was called. Long names are truncated—hover to see the full value. |
| Type | Original for a delivery triggered by the job, or Replay if the most recent attempt was a manual replay. |
| Status | Delivered (green) or Failed (red). Unknown (grey) appears if no status was recorded. |
| Response | The HTTP status code your endpoint returned, shown as a link. Click it to view the response body. A hyphen means no response was received—typically a connection failure or timeout. |
| Executed On | The date and time of the most recent delivery attempt. |
| Job | The job that ran the operation. Click to open it in the job builder. (Hidden when the page is filtered to a single job.) |
| Record | The record that triggered the job. Click to open it. If the record has since been deleted, the name is shown as plain text without a link. |
| Actions | Buttons to view job execution details and to replay a failed delivery. |
Viewing a Response Body
To see what your endpoint sent back, click the HTTP status code in the Response column. The Webhook Response modal displays the raw response body, with a Copy button so you can paste it into a ticket or a debugging session.
If your endpoint returned a status code but no body, the modal will show “No response body was returned from the webhook.”
Replaying a Failed Delivery
When a delivery fails because of a problem on your side, such as an endpoint that was down, an expired credential, or a misconfigured route, you can re-send the exact same payload once you’ve fixed it, without waiting for the job to trigger again.
Click the replay icon in the Actions column. The replay button appears only on rows with a Failed status.
A few things to know about replays:
- A replay is a single attempt. Unlike an original delivery, it is not retried automatically. If it fails, you can click replay again.
- The original payload is re-sent as-is. Risk Cloud does not rebuild the payload from the current state of the record, so the data your endpoint receives matches what was originally sent.
- The row updates in place. The Type changes to Replay, and Status, Response, and Executed On reflect the new attempt.
- A successful replay clears a failing webhook. If the webhook URL had been marked as failing, a successful replay returns it to active.
The replay button is unavailable in two cases and you can hover over the button to find out why.
| Tooltip | What to do |
|---|---|
| “This webhook has been deleted and cannot be replayed.” | The webhook URL no longer exists in Admin > Integration. Recreate it and update the job. |
| “This delivery attempt has no stored payload and cannot be replayed.” | The delivery predates payload storage. Trigger the job again to generate a new, replayable delivery. |
Viewing Job Execution Details
Click the details icon in the Actions column to open the job execution details modal for that run. The modal shows the full job execution, including the webhook operation’s URL, execution time, delivery status, and response code alongside every other operation the job performed.
Opening a Webhook’s Configuration
If you have the Admin - All entitlement, the name in the Webhook column is a link. Click it to open that webhook’s configuration modal directly, without navigating to Admin > Integration.
Data Retention
Webhook history is retained for 6 months, consistent with job execution history. Executions older than that are removed and no longer appear on the page.