Get Slack notifications for document activity
Connect a Slack workspace under Settings > Integrations, then route each of the eight document events to the channel that should hear about it.
Slack posts land once you connect a workspace and give each event a channel. Open Settings > Integrations, click Connect Slack on the card at the top, then click Configure and map the events you care about. This is a workspace admin job, and it's available on Growth and above.
Connect a Slack workspace
-
Open Settings > Integrations. The Slack notifications card is the first thing on the page.
-
Click Connect Slack. A Slack window opens where you pick the workspace and approve the app.
-
The card redraws with your Slack team name, a Connected badge and the date. Nothing is being posted yet, and the line under it says so: "No events are routed to Slack yet. Use Configure to map events to channels."
The Cloud storage card sits on this same page, so it's worth connecting Google Drive, Dropbox or OneDrive while you're here.
On a plan below Growth the Connect Slack button carries a small lock and clicking it opens the upgrade panel instead of Slack.
Route document events to channels
Click Configure to open the Slack event routing dialog. It's a table with three columns: Event, Channel and On.
Pick a channel for a row, flick its switch on, and repeat for anything else you want. The switch stays disabled until a channel is chosen, and clearing the channel turns the row off again. Click Save routing when you're done. Closing the dialog without saving discards the edits.
Eight events are available. They track the same lifecycle as the document statuses you see in the app:
| Event | Posts when |
|---|---|
| Document sent | An envelope was sent out for signature. |
| Recipient signed | A signer completed their part of an envelope. |
| Document completed | Every signer finished and the envelope is fully executed. |
| Recipient declined | A signer declined to sign. |
| Document cancelled | A sender cancelled an in-flight envelope. |
| Document expired | An envelope passed its expiry date before completion. |
| Recipient reassigned | A signing turn was handed to a different recipient. |
| Reminder sent | A signing reminder went out to a pending recipient. |
Several events can share one channel. Most teams start with Document completed in a deals channel and add the rest once they see the volume.
Post to a private channel
Private channels show with a padlock in the dropdown, and only after the app has been added to them. In Slack: open the channel, type /add in the message box and send it, choose to add apps to this channel, and pick Document eSign. Back in the routing dialog, click Refresh channels and the channel appears in every dropdown.
The same Refresh channels button is worth using after any channel rename or new channel creation, since the list is pulled when the dialog loads.
What happens next
Each routed event posts a message to its channel naming the document and the person involved. The card summary updates to read "Notifying 3 of 8 events to Slack", so you can see the shape of your setup without opening the dialog.
If a delivery fails, the row shows "Last delivery failed" with the reason, and an amber banner on the card tells you a routed channel is no longer reachable. Re-select a channel and save to clear it.
If something goes wrong
- The card is not on the page at all. You're signed in as a Member. Only admins and managers see it, and only admins can change anything.
- A red badge says Disconnected by Slack. Slack revoked our access, usually because the app was removed from the workspace. Click Reconnect and approve it again.
- An amber banner mentions an unreachable channel. The app was removed from that channel or the channel was archived. Open Configure, choose a channel again, and save.
- Slack is not configured on this server. That line replaces the card content when the integration has not been set up for this installation, and nothing on your side changes it.
- The Save routing button is grayed out. Nothing has changed since the dialog opened. Edit a channel or flip a switch and it wakes up.
- There is no Save routing button. The workspace has dropped below Growth, so the table is read-only and the footer offers Close in place of Cancel and Save routing.
Frequently asked questions
Who can connect and change Slack routing?
Only a workspace admin. Managers see the same card in read-only form and can open the routing dialog to look, without a Save button. A member who opens the integrations page sees the rest of it, but the Slack notifications card is not there for them at all.
Does connecting Slack turn off email notifications?
No, the two run side by side. Slack adds a second channel for document activity, and every email your workspace already sends carries on unchanged. Disconnecting Slack later stops the Slack posts only and leaves email exactly as it was.
Why is my private channel missing from the dropdown?
A private channel appears only after this app has been added to it. In Slack, open the channel, send the /add command, choose to add apps to the channel, and pick Document eSign. Then use Refresh channels in the routing dialog to pull it in.
What happens to my routing if I disconnect?
It is cleared. Disconnecting revokes the access token and stops every Slack post for the workspace, and the event-to-channel map goes with it. Reconnecting later gives you a fresh table with nothing routed, so you map the events you want again.
What happens if the workspace drops below Growth?
Whatever you already mapped keeps posting to Slack, and the card keeps showing your team name and its connected badge. The routing dialog turns read-only, the channel dropdowns and switches stop responding, and the Save routing button is gone entirely, leaving a Close button in the footer. Disconnect stays available so you can always leave.
Keep going
Connect Google Drive, Dropbox and OneDrive
Link a cloud storage account under Settings > Integrations so you can pull files into the send wizard, and so cloud backup has somewhere to write.
ReadWorkspace roles - Admin, Manager, Member and billing
What each of the three workspace roles can do, who is allowed to change a role, and why the last admin cannot be demoted or removed.
ReadDocument statuses explained
The six statuses a document can hold, what moves it from one to the next, the separate status each recipient carries, and why Scheduled is not on the list.
ReadChoose which emails you receive
Six event switches control the notifications sent to you. Transactional mail like verification codes and invitations always goes out, whatever you set here.
Read