Webhook Recipes

Use webhook recipes when you want a source system to send live issue changes to SLApulse.

SLApulse recommends the general webhook for new source integrations. The setup stays the same across source systems, and each source can have its own small copy/paste payload.

The payload is intentionally small and explicit. This makes it clear which data is sent to SLApulse, which also helps when you review the integration for GDPR or internal data-sharing rules.

Jira Automation

Use this recipe when Jira Automation sends issue changes to SLApulse.

Start with one Jira project and one test issue. After the first event arrives, check webhook diagnostics and then open the issue in SLApulse.

When to send the webhook

Create Jira Automation rules for the changes that matter to SLA tracking:

Jira change	Why it matters
Issue created	Sends the first known issue state to SLApulse.
Issue transitioned or status changed	Lets SLApulse apply your status mapping.
Priority changed	Lets SLApulse use the correct SLA target.
Issue type changed	Needed if your SLA filters or reports use issue type.

Set up the Jira action

In Jira Automation, add a Send web request action.

1. Copy the webhook URL from SLApulse.
2. Paste it into Jira without editing it manually.
3. Copy the webhook secret from SLApulse.
4. Add a request header named X-Webhook-Secret with the copied secret as the value.
5. Set the request method to POST.
6. Set the body type to custom JSON.
7. Add Content-Type: application/json if Jira asks for a content type header.
8. Paste this body:

{
  "issueKey": "{{issue.key}}",
  "sourceStatus": "{{issue.status.name}}",
  "sourceIssueType": "{{issue.issueType.name}}",
  "priority": "{{issue.priority.name}}",
  "createdAt": "{{issue.created.jiraDate}}"
}

Save the rule, then update a test issue in Jira. Check webhook diagnostics in SLApulse if the event does not arrive.

Data sent to SLApulse

The general webhook sends only the fields needed for SLA tracking and source matching.

Field	Jira value	Purpose
issueKey	Issue key	Identifies the source issue.
sourceStatus	Status name	Maps the Jira workflow status to SLA meaning in SLApulse.
sourceIssueType	Issue type name	Supports issue type filters and reporting.
priority	Priority name	Selects the matching SLA target.
createdAt	Issue created time	Preserves the original issue creation time.

This payload does not send issue descriptions, comments, reporter, assignee, labels, attachments, or other free-text fields.

SLApulse calculates the receive time and internal routing from the webhook URL and project setup.

Check the result

After the first test event:

1. Open webhook diagnostics in SLApulse.
2. Check that the event was accepted.
3. Open the issue in SLApulse.
4. Check that the source status appears as expected.
5. Map the status if the project is still collecting unmapped statuses.

If the webhook fails, copy the webhook URL and secret from SLApulse again. Do not build or edit the URL by hand.