SnagBane and Power Automate: a custom connector with a trigger per form

Start Power Automate flows when a SnagBane form is submitted — with every question as dynamic content — using the SnagBane custom connector or an HTTP trigger. Licence requirements and when you don't need Power Automate at all.

SnagBane works with Power Automate through a custom connector or an HTTP trigger. With the connector, flow makers get the trigger When a response is submitted, pick a form, and every question appears as its own dynamic content. Power Automate integration is part of the Business plan — and for many companies it isn't needed at all, because approvals and the Microsoft 365 actions are built into SnagBane.

First: do you need Power Automate?

GoalWithout Power Automate
Multi-stage approvals, reminders, reassigningBuilt into SnagBane — see approval workflows
A row in SharePoint or Excel after approvalSharePoint list and Excel integrations
A message in Teams, approvals in TeamsTeams integration and approvals in Teams
An entry in an Outlook calendarOutlook calendar integration
Anything else in your Microsoft 365 or other systemsPower Automate (below)

Both Power Automate options — the HTTP trigger and a custom connector — are Premium features in Power Automate: whoever builds or runs these flows needs a Power Automate Premium licence. People who only fill in the form need nothing.

  1. In SnagBane, open Automations & API and copy the connector address (…/integrations/power-automate/snagbane.swagger.json).
  2. In Power Automate: Custom connectors → New custom connector → Import from URL, name it SnagBane, paste the address, Create connector.
  3. In SnagBane click Create a token for Power Automate and paste the token when Power Automate asks for the API key.
  4. In a flow, choose When a response is submitted (SnagBane) and your form.

Every question is then its own dynamic content, next to the respondent's name, email, department and manager. The connector also has the actions List forms, Get responses and Get a response. Saved flows appear under Connected flows in SnagBane with their delivery log, and subscriptions are recorded in the audit log.

Option A: HTTP trigger (two minutes)

Create a flow with When an HTTP request is received, set Who can trigger the flow? to Anyone, paste SnagBane's JSON schema (Copy JSON schema on the form), and give SnagBane the flow's URL. Every request is signed, so the flow can verify it.

Run after approval

Like every SnagBane automation, a flow can run right away, after approval (once, after the last stage) or after rejection, so the flow never acts on a request that is later rejected.

Frequently asked questions

Does the respondent need a Power Automate licence?

No. Only the people who build or run the flows need Power Automate Premium.

Can a flow read older responses?

Yes. The connector's Get responses and Get a response actions read responses through the REST API.

See Power Automate in the documentation.

Try it on your own server

Free for teams up to 25 people. Install with Docker, on a VPS or on cPanel hosting.