Slack notifications
Get parser activity in a Slack channel via an incoming webhook.
Legacy integration: Slack notifications are not part of the default customer integration set. Access is gated by
NEXT_PUBLIC_ENABLE_SLACK_INTEGRATION. Existing webhook configurations may continue until removed.
The Slack integration posts parser activity to a channel of your choice. It is notifications only: Slack is not a data destination, and extracted data is delivered through your destinations.
Setup
- In Slack, create an incoming webhook for the channel that should receive notifications (Slack: Apps → Incoming Webhooks).
- In Parsedit, open Integrations → Slack and paste the webhook URL.
- Choose which events to receive.
Events
| Event | Default | When it fires |
|---|---|---|
| Document received | Off | A document arrives via any intake channel |
| Extraction complete | On | Processing finished, document ready for review |
| Extraction failed | On | Processing could not finish |
| Sent to destination | On | Data was delivered to a destination |
| Delivery failed | On | A destination send did not succeed |
Messages include the parser name, file name, and a link back to the document. You can optionally include a short summary of extracted field values in completion messages.
Typical use
Slack pairs well with automated intake: documents arrive by email or webhook, extraction runs unattended, and your team gets pinged only when something completes or needs attention.