> ## Documentation Index
> Fetch the complete documentation index at: https://docs.satyakod.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Zapier, Slack and Splunk

> Send Satyakod events to Zapier and Slack, and the audit trail to Splunk.

Admins set these up in **Settings → Integrations**. Zapier and Slack depend on your plan. For your
own systems, [webhooks](https://docs.satyakod.com/integrations/webhooks.md) are usually simpler: they carry the same events,
signed.

## Slack

Satyakod posts events (`alert.created`, `alert.updated`, `batch.signed`, `batch.revoked`,
`scan.flagged`) to the Slack channels you choose.

**1. Connect**

**Slack → Connect → Connect Slack**. Slack opens in a new tab and asks you to approve the
Satyakod app for your Slack workspace; approve it and come back.

**2. Read your channels**

**Refresh channels** reads your Slack channels. For a private channel, invite the Satyakod app
to it first, then refresh.

**3. Add rules**

**Add rule**: pick the events and the channels they post to. Add as many rules as you need,
for example counterfeit alerts to `#brand-protection` and signed batches to the plant's channel.

**Disconnect** stops posting. If Slack revokes access (the app was removed from Slack), the card
says *Needs attention*: disconnect and connect again.

Slack is for your team's channels; who is notified of an alert, and how, is set with the
[alert rules](https://docs.satyakod.com/guides/alerts.md).

## Zapier

Zapier receives the same events as webhooks. In Zapier, choose a Satyakod trigger and sign in with
an [API key](https://docs.satyakod.com/api-reference/introduction.md) that has the `webhooks:write` scope. Each Zap you turn on
appears under **Zapier → Manage Zaps**, with its event and last delivery; **Disconnect** stops
sending to it. After five failed deliveries in a row a Zap is stopped; turn it off and on in
Zapier to start it again.

## Splunk

Satyakod streams the workspace's audit trail (changes and sign-ins) to a Splunk HTTP Event
Collector.

1. In Splunk, create a token under **Settings → Data inputs → HTTP Event Collector**.
2. In Satyakod, **Splunk → Connect**: enter the collector's address (`https://`, reachable from
   the internet, for example `https://splunk.example.com:8088`), the token, and the index and
   source type (`main` and `satyakod_audit` by default).
3. **Connect** sends a test event and saves only if Splunk accepts it. The token is stored
   encrypted; leave it blank later to keep it.

**Disconnect** stops streaming.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.