Skip to content
Quenza
MCPNew: use this help center in Claude, ChatGPT or CursorConnect →

What you can build

3 min read

Ideas and a quick start for the Quenza API, from filling group courses from your shop to a weekly task digest for your team.

Quenza is where your sessions, activities and conversations happen. The API connects it to everything around them: your website and shop, your CRM, your booking tool, your team’s chat and your own reports. Each idea below takes a few requests and saves someone a little typing every day, and together they add up to a practice that runs more smoothly.

  1. Get a token. A workspace Owner or Manager creates it under Developer Tools → API Token. See Authentication.
  2. Make your first request. List your clients with the example in the Introduction. Every endpoint page has the same request in curl, JavaScript, Python and PHP, ready to copy.
  3. Pick an idea. Start with one of the guides below, or combine the endpoints your own way.

No developer at hand? Zapier and Make can send the same requests with an HTTP step, and they can receive Quenza’s webhooks.

Someone buys a place in your eight-week course on your website. Seconds later they have their invitation, sit in the group chat and have the first week’s activities, also when the course already started. Add buyers to a group

A lead marked as booked in your CRM becomes a client in Quenza, and new details flow over without copying. With the Client Invitation Accepted webhook, the CRM also learns when a client has set up their account. Sync clients from your CRM

Never lose a client to an unopened invitation

Section titled “Never lose a client to an unopened invitation”

Every Monday, your coaches get a short list of clients who were invited more than a week ago and have not started yet, so they can send a friendly reminder before the client’s motivation fades. Follow up on invitations

Each member of your team gets their open tasks for the week in Slack or by email: what is overdue, what is due soon, and for which client. Weekly task digest

When someone books their first session in your booking tool, create the client. Their invitation is waiting when they arrive, and the intake questionnaire can be sent before the first session instead of after it.

When a new coach is added to your HR or staff planning tool, create them as a member with the role member, and keep their phone number and address in step with Update a member. Suspending someone who leaves is done in Quenza; see Suspend and reactivate.

When a coaching package ends in your billing or booking tool, archive the client, so running activities stop and the chat becomes read-only. When they book again, unarchive them and pick up where you left off.

List clients and list tasks once a night and write the numbers to a spreadsheet: active, pending and archived clients, new clients per month, tasks completed per week. A chart in Google Sheets or Looker Studio then shows how the practice grows.

Run a programme for a partner organisation

Section titled “Run a programme for a partner organisation”

A company books your stress programme for 30 employees. Create a group for the company, then create the employees from the list HR sends you and add them to the group in one request. Everyone is invited the same morning.

The API works with clients, groups, team members and tasks. It cannot send activities or programs, read activity results, notes or chats, or list groups. Groups can send their activities to new members automatically, which covers most course and programme ideas; see New group members.

Enlarged screenshot from this article