Steppd is built to route process context into the tools your team already uses. Rather than storing SOPs in a silo, you can wire Steppd events directly into your automation stack, push structured document data into downstream systems, and keep everything in sync without manual steps. Two integration layers are available on the Scale plan: outbound webhooks and a REST API.Documentation Index
Fetch the complete documentation index at: https://docs.steppd.com/llms.txt
Use this file to discover all available pages before exploring further.
Webhooks and the REST API are available on the Scale plan only. Upgrade from Settings → Billing to enable them.
Integration layers
Webhooks
Steppd sends an outbound HTTP POST to any URL you configure when lifecycle events fire. There are eight event types covering the full document and member lifecycle, from creation and publishing through revision, archiving, assignment, and membership changes. You can point webhook events at any automation platform, Zapier, Make, n8n, Pipedream, Gumloop, and others, and route the structured payload into the downstream tools that depend on your process data. Each webhook includes a signing secret so you can verify that the payload came from Steppd.REST API
The REST API lets you pull published document data programmatically using an API key. Authenticate with a Bearer token, reference a document by ID, and retrieve its full structured content, sections, steps, sub-steps, and metadata, in a single request.What you can build
These are practical, ready-to-use examples based on real workflows teams have built with Steppd.Notify Slack when an SOP is published
Notify Slack when an SOP is published
Fire the
document.published event to Zapier and post a formatted message to your #ops or #team Slack channel every time a process goes live.Log new SOPs to Google Sheets
Log new SOPs to Google Sheets
Use the
document.created event to append a row to a running spreadsheet, capturing the title, department, author, and timestamp for every new SOP.Create a Jira ticket when an SOP is revised
Create a Jira ticket when an SOP is revised
Trigger the
document.revised event to open a Jira task prompting your team to review the new revision before it rolls out.Create a Trello card when an SOP is assigned
Create a Trello card when an SOP is assigned
Use
document.assigned to automatically create a Trello card so teammates can action a newly assigned process without checking Steppd.Sync published SOPs to Notion
Sync published SOPs to Notion
Trigger
document.published via n8n to create a Notion database page for every published document, mapped to your fields.Send onboarding docs to new hires via email
Send onboarding docs to new hires via email
Combine an HRIS webhook with Steppd’s REST API to automatically email the latest onboarding SOP to a new hire when their record is created.
Send an email digest when SOPs are archived
Send an email digest when SOPs are archived
Use
document.archived to email your team a summary whenever a process is retired, so nothing disappears without notice.Save published SOPs to Google Drive
Save published SOPs to Google Drive
Trigger
document.published via Make to create a Google Doc stub for every new SOP, available for offline reference or sharing outside the organization.Push to Zendesk and a vector database for AI/RAG
Push to Zendesk and a vector database for AI/RAG
Use
document.published to push the latest policy copy to Zendesk and simultaneously load it into a vector store so your AI support agents always have current context.Explore the integrations
Webhooks
Set up outbound HTTP event delivery for the 8 document and member lifecycle events.
API keys
Create API keys and pull published document data programmatically.
Automation Assistant
Describe what you want to automate and get a ready-to-use recipe for your platform.