Webhooks [BETA]

What is a webhook, and why would I use one?

Normally, if you want to know what is happening in Electric IT Management, you have to log in and check. A webhook turns that around. You give Electric a secure web address belonging to one of your own systems, and the moment something relevant happens, Electric sends that address a notification with the details.

You do not need to be a developer to benefit from this. Tools your team already uses, including Jira Service Management and Slack, can receive these notifications and act on them with no code required.

Electric can send events to Jira Service Management, to Slack, or to any secure endpoint you control.

Some things teams commonly use webhooks for:

• Employee lifecycle. Create a Jira work item the moment a new hire is added, so their laptop and accounts are queued before day one. Post to Slack when someone is offboarded, so whoever is on duty knows to revoke access right away. Send updates to your own system to keep records in step as job titles and emails change.

• Employee group membership. Create a Jira work item when someone joins a group that carries software access, so a licence gets assigned. Or post to Slack for a running record of who gained access to what, and when.

• Groups & membership. Post to Slack when a group is created, changed, or deleted, so a new access boundary does not appear unnoticed. Send the same events to your own system to keep an access model in step with Electric.

• Tasks. Mirror Support Center tickets into Jira so your team works from a single queue. Onboarding and offboarding raise task events too, so that whole checklist can land in your own tracker.

Before you start

• You will need Admin access in Electric. Viewing webhooks requires the webhooks read permission, and creating, editing, or deleting them requires the webhooks write permission.

• You will need somewhere for the notification to go: a secure address you control, or an incoming webhook from a tool you already use.

• Electric requires a valid, secure (HTTPS) address that resolves to a public host. Plain unsecured addresses, and addresses that resolve to internal or private networks, are rejected.

• Each organization can create up to 20 webhooks.

Important: Set up your destination system first. You will need its address, and for Jira Service Management its token, before you can finish creating the webhook in Electric.

Choosing a provider

Electric shapes each notification for its destination, so the first thing you choose is a provider.

If you paste an address that matches one of these hosts, Electric selects the matching provider for you and shows a banner reading Provider updated automatically. You can change the provider yourself at any time.

What each topic sends you

Every notification tells you which topic it came from, which event fired, when it happened, and includes a data section with the details.

Important: The topic named Tasks delivers events named request.created, request.completed, and so on. If you are matching on the event name in your own system, use the request. names rather than the word "task".

Every notification has the same outer shape. What changes from event to event is the topic, the event name, and the contents of data.

Payload Preview

Here is an example of the payload of each event, grouped by topic.

Employee lifecycle

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456701",
  "topic": "employee.lifecycle",
  "event": "employee.created",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "22222222-2222-2222-2222-222222222222",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "job_title": "Software Engineer",
    "status": "ACTIVE",
    "start_date": null,
    "group_ids": []
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456702",
  "topic": "employee.lifecycle",
  "event": "employee.updated",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "22222222-2222-2222-2222-222222222222",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "job_title": "Senior Software Engineer",
    "status": "ACTIVE",
    "start_date": null,
    "group_ids": []
  },
  "previous_attributes": {
    "job_title": "Software Engineer"
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456703",
  "topic": "employee.lifecycle",
  "event": "employee.offboarded",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "22222222-2222-2222-2222-222222222222",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "job_title": "Software Engineer",
    "status": "INACTIVE",
    "start_date": null,
    "group_ids": []
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456704",
  "topic": "employee.lifecycle",
  "event": "employee.reactivated",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "22222222-2222-2222-2222-222222222222",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "job_title": "Software Engineer",
    "status": "ACTIVE",
    "start_date": null,
    "group_ids": []
  }
}

Employee group membership

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456705",
  "topic": "employee.groups",
  "event": "employee.group_added",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "22222222-2222-2222-2222-222222222222",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "job_title": "Software Engineer",
    "status": "ACTIVE",
    "start_date": null,
    "group_ids": [
      "33333333-3333-3333-3333-333333333333"
    ],
    "affected_group_id": "33333333-3333-3333-3333-333333333333",
    "affected_group_name": "Engineering"
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456706",
  "topic": "employee.groups",
  "event": "employee.group_removed",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "22222222-2222-2222-2222-222222222222",
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "job_title": "Software Engineer",
    "status": "ACTIVE",
    "start_date": null,
    "group_ids": [],
    "affected_group_id": "33333333-3333-3333-3333-333333333333",
    "affected_group_name": "Engineering"
  }
}

Groups & membership

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456707",
  "topic": "groups",
  "event": "group.created",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "33333333-3333-3333-3333-333333333333",
    "name": "Engineering",
    "parent_group_id": null,
    "employees_count": 0
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456708",
  "topic": "groups",
  "event": "group.updated",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "33333333-3333-3333-3333-333333333333",
    "name": "Engineering (Platform)",
    "parent_group_id": null,
    "employees_count": 12
  },
  "previous_attributes": {
    "name": "Engineering"
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456709",
  "topic": "groups",
  "event": "group.deleted",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "id": "33333333-3333-3333-3333-333333333333"
  }
}

Tasks

Remember that the Tasks topic uses the topic key requests.lifecycle and request. event names.

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456710",
  "topic": "requests.lifecycle",
  "event": "request.created",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "request_id": "44444444-4444-4444-4444-444444444444",
    "request_type_slug": "get_access_or_license",
    "request_type_category_slug": "applications",
    "request_title": "Grant access to Slack",
    "requester": {
      "type": "user",
      "id": "55555555-5555-5555-5555-555555555555",
      "name": "Sam Lee",
      "email": "sam.lee@example.com"
    },
    "assignee_id": null,
    "assignee": null,
    "on_behalf_of_id": "22222222-2222-2222-2222-222222222222",
    "on_behalf_of": {
      "id": "22222222-2222-2222-2222-222222222222",
      "name": "Jane Doe",
      "email": "jane.doe@example.com"
    }
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456711",
  "topic": "requests.lifecycle",
  "event": "request.completed",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "request_id": "44444444-4444-4444-4444-444444444444",
    "request_type_slug": "get_access_or_license",
    "request_type_category_slug": "applications",
    "request_title": "Grant access to Slack",
    "requester": {
      "type": "user",
      "id": "55555555-5555-5555-5555-555555555555",
      "name": "Sam Lee",
      "email": "sam.lee@example.com"
    },
    "assignee_id": "66666666-6666-6666-6666-666666666666",
    "assignee": {
      "id": "66666666-6666-6666-6666-666666666666",
      "name": "Alex Kim",
      "email": "alex.kim@example.com"
    },
    "on_behalf_of_id": "22222222-2222-2222-2222-222222222222",
    "on_behalf_of": {
      "id": "22222222-2222-2222-2222-222222222222",
      "name": "Jane Doe",
      "email": "jane.doe@example.com"
    }
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456712",
  "topic": "requests.lifecycle",
  "event": "request.canceled",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "request_id": "44444444-4444-4444-4444-444444444444",
    "request_type_slug": "get_access_or_license",
    "request_type_category_slug": "applications",
    "request_title": "Grant access to Slack",
    "requester": {
      "type": "user",
      "id": "55555555-5555-5555-5555-555555555555",
      "name": "Sam Lee",
      "email": "sam.lee@example.com"
    },
    "assignee_id": "66666666-6666-6666-6666-666666666666",
    "assignee": {
      "id": "66666666-6666-6666-6666-666666666666",
      "name": "Alex Kim",
      "email": "alex.kim@example.com"
    },
    "on_behalf_of_id": "22222222-2222-2222-2222-222222222222",
    "on_behalf_of": {
      "id": "22222222-2222-2222-2222-222222222222",
      "name": "Jane Doe",
      "email": "jane.doe@example.com"
    }
  }
}

{
  "id": "evt_0a1b2c3d-4e5f-6789-abcd-ef0123456713",
  "topic": "requests.lifecycle",
  "event": "request.automation_failed",
  "created_at": "2026-09-28T14:20:06.596813+00:00",
  "org_id": "11111111-1111-1111-1111-111111111111",
  "test": false,
  "data": {
    "request_id": "44444444-4444-4444-4444-444444444444",
    "request_type_slug": "get_access_or_license",
    "request_type_category_slug": "applications",
    "request_title": "Grant access to Slack",
    "requester": {
      "type": "user",
      "id": "55555555-5555-5555-5555-555555555555",
      "name": "Sam Lee",
      "email": "sam.lee@example.com"
    },
    "assignee_id": null,
    "assignee": null,
    "on_behalf_of_id": "22222222-2222-2222-2222-222222222222",
    "on_behalf_of": {
      "id": "22222222-2222-2222-2222-222222222222",
      "name": "Jane Doe",
      "email": "jane.doe@example.com"
    }
  }
}

On an update event, the notification also carries a previous_attributes section listing only the fields that changed, for example "previous_attributes": {"job_title": "Support Engineer"}. This is useful when you only want to react to a particular field changing.

A few behaviors worth knowing:

• employee.reactivated fires only for employees who were previously offboarded, never for newly created ones.

• Group membership events fire once per group, so a change affecting three groups sends three notifications.

• group.deleted arrives with only the group's id, because the group no longer exists by the time the event is sent.

Sending to your own endpoint

Choose Generic webhook when you are sending events to a service you run yourself, or to an automation platform such as Zapier or Make. Electric posts its standard notification exactly as shown above, with no reshaping for a particular destination.

Steps in Electric:

1. Log in to Electric

2. Select Settings, then the Webhooks tab

3. Click Create webhook

4. Select Generic webhook as the provider

5. Enter a Name for the webhook

6. Paste your Endpoint URL. There is nothing else to fill in, because the generic provider has no credentials or settings of its own

7. Select your topics

8. Review the payload preview so you know the exact shape your service will receive

9. Leave Active turned on, then Click Create webhook

10. You are all set!

What your endpoint needs to do

• Accept an HTTP POST with a JSON body. Electric sends Content-Type: application/json and identifies itself with User-Agent: Electric-Webhooks/1.0.

• Respond within 10 seconds. Anything slower is recorded as a failure and is not sent again. If your processing takes longer than that, acknowledge the notification first and do the work afterwards.

• Return a status in the 200 range. Anything else is recorded as a failure. Redirects are not followed, so a 301 or 302 is treated as a failed delivery rather than passed along to the new address.

Address requirements

• The address must use HTTPS. Electric will not save a plain HTTP address.

• The host must be publicly resolvable. Addresses that resolve to private, loopback, link-local, reserved, multicast, or carrier-grade NAT ranges are rejected. Electric checks this when you save and again at the moment of delivery, so an address that later points inward stops working rather than being delivered to.

• Unlike Jira Service Management and Slack, the generic provider places no restriction on which host you use.

Recognizing repeat deliveries

Every notification carries an id at the top level. If the same event reaches you more than once, that id stays the same, so your service can record what it has already handled and safely ignore repeats.

Two other details that make parsing easier. Fields with no value arrive as JSON null rather than being left out, so the shape of data stays consistent for a given event type. And test tells you whether the notification came from a test send or a real event.

No native option in your helpdesk? Automation platforms such as Zapier and Make connect to almost any helpdesk without code. Create a Catch Hook trigger, paste the address it gives you into Electric as your endpoint URL, send a test event so the platform has a sample to work with, then add your helpdesk's create-ticket action and map the fields.

Do not have a receiver set up yet? Point your webhook at a free tool such as webhook.site temporarily. It gives you a disposable address and shows the exact notification as it arrives, which is a good way to confirm everything on Electric's side works before wiring it into a real system.

Testing your webhook

Before pointing a webhook at something important, send a test notification.

• While creating or editing a webhook, click Send test event in the payload preview panel. This works before you have saved the webhook, and shows the real response from your address.

• For a saved webhook, select Send test event from its row menu on the Webhooks list, or from its detail page.

Test notifications use sample data, a fictional employee or task, and are marked "test": true, so nothing you send while testing looks like a real record on the receiving end.

Electric reports the result as a message on screen. Only a response in the 200 range counts as delivered. A redirect is treated as a failure, and Electric does not follow it.

Important: A successful response means your address accepted the request. It does not confirm the destination did anything useful with it. A Jira rule with an incorrect field mapping still returns a success, so check the destination as well.

Please note: Test events are not added to the delivery log. If you have only ever sent test events, Recent deliveries will still be empty. That is expected, and does not mean the test failed.

In Jira Service Management you can confirm from the other side. Open your rule and view its Audit log to see what Jira received and what it did with it. Atlassian's verification guide covers this in more detail.

Checking delivery history

Open a webhook to see Recent deliveries, which shows the 50 most recent real events, newest first.

You can filter the list by All, Success, or Failure.

Please note: Failed rows show a Retry link. It does not resend the original notification. It sends a fresh test event to the same address, so you can check whether your endpoint is working again, and it leaves the failed row as it was.

The log records this summary only. It does not store the contents of the notification or of the response.

Please note: The delivery list does not update on its own. Reload the page to see recent activity.

Limits and delivery behavior

Important: Delivery is best effort. Electric attempts each notification once and does not try again. If your endpoint is unavailable or slow to respond, that event is recorded as failed and is not resent. If your endpoint has been down, treat the delivery log as a record of what was missed rather than a queue that will catch up.

Managing your webhooks

From the Webhooks list, use the menu at the end of any row to edit a webhook, send a test event, enable or disable it, or delete it.

Turning a webhook off stops deliveries immediately. Its settings are kept, so you can turn it back on at any time. Deleting a webhook removes it and its delivery history permanently, and cannot be undone.

FAQ

I sent a test event and got a success message, but Recent deliveries is empty. Is it broken?

No. Test events are not recorded in the delivery log. The log fills in once real events start firing. Bear in mind that the list also does not refresh on its own, so reload the page after you expect an event.

Are deliveries signed, so my endpoint can verify they came from Electric?

Not today. Signature verification is planned but not yet available, and the signing secret shown on the webhook detail page reads Not enabled for this reason. In the meantime, verify deliveries another way: include a secret value in the endpoint address itself, or restrict your endpoint to traffic you expect.

Why does the Tasks topic send events called request.created?

The topic is named for what you see in Electric, while the event names follow the underlying record. They refer to the same thing. Match on the request. names when you write rules in another system.

Can I subscribe to just one event within a topic?

No. Subscribing to a topic delivers every event within it. You can filter on the event field in your receiving system.

Can one webhook post to several Slack channels?

No. A Slack incoming webhook posts to a single channel. Create a separate incoming webhook in Slack and a separate webhook in Electric for each channel.

I filled in the form and it failed without telling me why.

Two things cause this. Check how many webhooks you already have, since each organization is limited to 20 and the count appears above the list. Also check that the name is not already in use, because webhook names must be unique within your organization. Neither of these is named in the error message.

Please contact our team at support@electric.ai if you have any questions or need any additional information with setting up your webhooks.