Statuspage by Atlassian is an incident communication platform for building and managing public or private status pages. Communicate real-time service status to customers via components, incidents, and subscriber notifications.
Paperform connects to Statuspage directly through Stepper workflows.
Each submission can reach Statuspage as structured data, ready for your own systems and code.
How Statuspage connects to Paperform
Direct methods run inside your Paperform account. Zapier and Make are there too if your team already uses them.
Run a Stepper workflow when someone submits your form: 9 Statuspage actions and 3 triggers, included in your Paperform account.
- Open Stepper from your Paperform account and create a workflow.
- Start it with the Paperform “New Submission” trigger and choose your form.
- Add a Statuspage step, connect your account and map the submission’s answers to its fields.
Statuspage actions in Stepper
- Create Incident
- Update Incident
- Create Component
- Update Component
- Delete Component
- Create Subscriber
- List Incidents
- List Components
- Make HTTP Request
Statuspage events that can start a workflow
- New Incident
- New Component Status Change
- New Subscriber
What your form sends to Statuspage
For example, with a Stepper workflow the “Create Incident” action takes these fields. Map each one to a question
on your form, and every submission fills them in.
| Statuspage field | Question on your form | Required |
|---|
| Page | Dropdown or choice | Yes |
| Incident Name | Short answer | Yes |
| Status | Dropdown or choice | Yes |
| Impact | Dropdown or choice | No |
| Message | Long answer | No |
| Affected Components | Dropdown or choice | No |
| Send Notifications | Yes/No | No |
Start from a template
Pick a template, then connect it to Statuspage. There are 30,000+ in the
templates directory.
Related
More developer tools integrations