Recipes
Complete, working integrations you can copy and adapt, each with test-mode steps and a production checklist.
This is designed and scheduled but not built yet. We document it now so you can plan your integration.
Each recipe solves one real problem from start to finish: what you need, every step, complete code, how to try it safely in test mode, and what to check before going live.
The recipes use the preview API contract and the planned TypeScript SDK, so you can read them and plan your integration now. They'll run as written once the API and SDK are released.
| Recipe | You'll build | Plan | Uses |
|---|---|---|---|
| Pre-register visitors from your CRM | When a client meeting is booked in your CRM, the client gets an Agoo pass, and the CRM learns when they arrive | Pro | API, webhooks, TypeScript |
| A live on-site list in Slack | One Slack message per site that always shows who is in the building | Pro | API, webhooks, TypeScript |
| Attendance to payroll | A monthly job that turns Agoo attendance into your payroll team's spreadsheet | Pro | API, TypeScript, CI |
| A booking widget on your site | Online booking on your own website, with your server told about every booking | Any plan with booking pages; Growth for the webhook | Embed, webhooks, PHP or TypeScript |
Every recipe can be built and tested on any plan in test mode, where nothing is sent to real people.
Before you start
- Create a test key in Console → Developers → API keys with only the scopes the recipe lists. See authentication.
- Keep keys in environment variables, never in code or version control.
- Install the CLI to receive webhooks on your machine while you build:
agoo listen --forward-to …. See CLI.
Related
HR and payroll
Import staff from a CSV file, export timesheets in payroll-ready formats, and keep Agoo in step with your HR system.
Pre-register visitors from your CRM
When a client meeting is booked in your CRM, create an Agoo visit and send the client a QR pass, keep it in step with changes, and tell the CRM when they arrive.