Send Izini events to Slack, Teams, Jira or Google Sheets

Izini sends a signed webhook when something needs attention: a data subject request arrives or falls due, a breach's 72-hour clock moves, a policy is published, and more (the full list). These recipes take those events into the tools your team already uses, through n8n (which you can run yourself or use as a service) or Make.

You need: an n8n or Make account, a paid Izini plan or a trial, and the tool you want the events in.

Recipe	What it does	n8n	Make
Slack	Posts each event to a channel, with the reference, the date and a link to Izini.	n8n-izini-to-slack.json	make-izini-to-slack.json
Microsoft Teams	The same, in a Teams channel. Needs a work or school Microsoft 365 account.	n8n-izini-to-teams.json	make-izini-to-teams.json
Jira	Opens an issue when a request arrives or an incident is logged, and adds a comment as it falls due, the breach clock moves or it closes.	n8n-izini-to-jira.json
Google Sheets	Adds a row for every event: a running log your team can filter and share.	n8n-izini-to-google-sheets.json

The steps below are for n8n; Make is further down.

1. Download the recipe.
2. In n8n, open Workflows, choose Create workflow, then in the … menu choose Import from File and pick the file.
3. The note at the top lists the three settings below.

1. Your webhook secret. Add the webhook in Izini first (step 4) to get its secret, then paste it into the node Sign with your webhook secret, replacing PASTE_YOUR_IZINI_WEBHOOK_SECRET.
2. Your account in the tool. Open the last node (Post to Slack, Post to Teams, Open a Jira issue or Add a row), connect your account, and choose the channel, project or sheet. For Google Sheets, first make a sheet with the columns Received, Event, Headline, Reference, Date, Project, Delivery and Link.
3. Activate. Switch the workflow on, open the node Izini webhook, and copy its Production URL.

1. In the Izini dashboard, open Developers > Webhooks and choose Add webhook.
2. Paste the production URL from n8n and choose the events. For the Jira recipe, choose at least dsar.received and incident.created; add dsar.due_soon, dsar.overdue, dsar.closed, incident.breach_clock and incident.ndpc_notified to have them added as comments.
3. Copy the webhook's secret into n8n (step 3.1) and save the workflow. Izini shows the secret once, when you add the webhook; if it is lost, use Rotate secret.

Izini sends the next matching event within about a minute. Each webhook's Deliveries in Izini shows what was sent and what n8n answered; Send again repeats one for testing.

1. Download the Make recipe. In Make, create a scenario, open the … menu at the bottom and choose Import Blueprint, then pick the file.
2. Open the first module, Izini webhook, and add a webhook. Under Show advanced settings, turn on Get request headers and JSON pass-through: the signature check needs the headers and the exact text Izini sent. Copy the webhook's address.
3. Open Sign with your webhook secret and, in the expected value, replace PASTE_YOUR_IZINI_WEBHOOK_SECRET with your webhook's secret from Izini.
4. Open Post to Slack or Post to Teams, add your connection, and choose the channel (Slack: type it, such as #compliance; Teams: pick the team and channel).
5. In Izini, add the Make webhook address under Developers > Webhooks with the events you want, and switch the scenario on.

• Only Izini's requests get through. The first steps work out the signature from the raw request and your secret, and compare it with X-Izini-Signature-V2. A request with a wrong signature, or one signed more than five minutes ago, gets 401 and goes no further. This is the same check as in the reference.
• A retry is handled once (n8n). Izini resends a delivery your endpoint did not accept, with the same id. In n8n, Skip repeats remembers the ids it has seen, so a retried event is not posted twice. Make has no built-in equivalent; since the scenario answers at once, Izini only retries when Make itself was unreachable, and then a message can appear twice.
• Izini hears back at once. The workflow or scenario answers 200 as soon as the signature checks out, before it posts anywhere, so a slow Slack or Jira never makes Izini think the delivery failed.
• No personal details travel. The events carry ids, references, statuses and dates, never a data subject's name or contact details, and the recipes add nothing more. Jira issues and Slack messages link back to the record in Izini.

• In Izini, the delivery says 404: the workflow is not active, or the URL is the test URL. Use the production URL and switch the workflow on.
• 401: the secret in Sign with your webhook secret does not match this webhook's secret, or the n8n server's clock is more than five minutes out. In Make, also check that the webhook has Get request headers and JSON pass-through turned on.
• 200, but nothing in the channel or project: open the workflow's Executions in n8n, or the scenario's History in Make; the failing step shows the error from Slack, Teams, Jira or Google.
• Who: organisation admins and owners manage webhooks, and so can a team member they give the Privacy Engineer / IT Lead role. Other members can see webhooks and their deliveries.
• The plan: webhooks come with every paid plan and with a trial. Izini says so in Developers > Webhooks if yours does not include them.