Skip to main content
This recipe starts a Zap each time a new application arrives on your waiting list. It uses Webhooks by Zapier, which needs a paid Zapier plan.

​
1. Set up the trigger

1

Choose the trigger

Create a Zap. For the trigger, choose Webhooks by Zapier, then Retrieve Poll.
2

Fill in the request

  • URL: https://api-demo.scoutworks.app/api/v1/waiting-list?status=received&limit=200
  • Key: data (the list inside the response)
  • Deduplication Key: id (so each entry starts the Zap once)
  • Headers: Authorization → Bearer followed by the key, for example:
3

Test it

Choose Test trigger. Zapier shows entries from the demo group.
Zapier checks the list every few minutes, depending on your plan. It starts the Zap once for each entry it has not seen before.

​
2. Add an action

Add any action. For example, Slack → Send Channel Message, with the message:
Each […] is a field you insert from the list Zapier shows. The API reference describes each one.

​
3. Switch to your group

In the trigger, change api-demo.scoutworks.app to api.scoutworks.app, and replace the sandbox key with your own. Your key needs the waiting-list:read scope. Add waiting-list.contacts:read if the Zap needs parent contact details.

​
Limits

  • Retrieve Poll reads one page. The list comes oldest first, so the recipe asks only for applications still at received, the first stage. Once a leader moves an application on, it leaves that list. If more than 200 applications sit at received, Zapier cannot see the newest ones. To copy a whole list, use n8n, Google Sheets or Python.
  • Google Sheets actions. If a Zap writes names into a sheet, a name that starts with = can run as a formula. Add a Formatter step that puts ' in front of values that start with =, +, - or @.
  • A ready-made Scoutworks app for Zapier and n8n is on our list. Until then, this recipe does the same job.