Skip to content
More from us
SpeedPy Django SaaS boilerplate Appliku Deploy on your own servers

Make & n8n

There is no dedicated Make or n8n app yet, but both automate withfeedback fine over the generic webhooks and a personal access token. The shape is the same in either tool.

You need a plan with API access (Pro and above).

1. Get a token

Create a personal access token with the scopes you need — read:feedback to read submissions, write:webhooks to register endpoints, moderate:submissions to approve/reject. Send it as Authorization: Bearer <token>.

2. Subscribe an endpoint

Add a Webhook/Trigger node in Make or n8n and copy its URL. Register it, either on the Settings → Webhooks page or over the API:

POST /api/v1/teams/{team_id}/webhooks/
Authorization: Bearer <token>
Content-Type: application/json

{ "url": "https://hook.eu2.make.com/…", "events": ["submission.approved"] }

The response includes a one-time signing_secret — store it in your scenario for step 3.

3. Verify each delivery

We POST the event envelope with X-SpeedPy-Signature (HMAC-SHA256 over "{timestamp}." + raw_body). Verify it before acting — see Verifying a delivery. Then answer 200 quickly and do the work afterwards.

4. Hydrate the submission

The payload is intentionally small (ids + a little context). To get the full submission — text, rating, contact, tags — read it back:

GET /api/v1/teams/{team_id}/submissions/{submission_id}/
Authorization: Bearer <token>

Keep it healthy

  • If your scenario is deleted or paused, answer 410 Gone on its URL (or delete the endpoint) so we stop delivering — otherwise every event becomes a failed attempt.
  • Deliveries are at-least-once; deduplicate on X-SpeedPy-Delivery.
  • Endpoints stop when the team loses API access, the token's owner leaves the team, or the token is revoked. See When an endpoint stops delivering.