Skip to main content
Connect CoachIQ to the tools you already use. Zapier lets you send data out of CoachIQ automatically whenever something happens — a new athlete signs up, a session is booked, a form is submitted — without any code.
Where to find this: Settings → Developer → API Keys

​
One-time setup

1

Add CoachIQ to your Zapier account

The CoachIQ Zapier app is private and won’t appear if you search Zapier’s app directory. You must accept the invite link first.Open the link below while signed in to Zapier, then click Accept Invite & Build a Zap:Accept the CoachIQ Zapier invite →CoachIQ is now available when you search for an app inside any Zap. You only do this once per Zapier account.
2

Get your Group ID and API Key from CoachIQ

In CoachIQ, go to Settings → Developer → API Keys.Group ID: Click the Copy button next to your Group ID and save it somewhere handy.
The API Keys page shows two copy buttons — Org ID and Group ID. Zapier requires the Group ID. Copying the Org ID by mistake will cause an “Unauthorized” error when connecting.
API Key: Click + New API Key, give it a name (e.g. “Zapier”), then copy the key immediately.
Your API Key is 128 characters long and is shown only once — when you leave the page, it’s gone. If you lose it, create a new one. You can have up to 10 keys per group.
3

Connect CoachIQ in Zapier

In Zapier, start a new Zap and add CoachIQ as the trigger or action app. When Zapier asks you to connect an account, a small window opens with two fields:Click Yes, Continue. Zapier saves this as a reusable CoachIQ connection — you won’t need to enter these again for future Zaps.
4

Test the connection

Zapier automatically runs an authorization check. A green check means you’re connected. If you see Unauthorized, re-copy both values from CoachIQ and try again — the most common cause is accidentally pasting the Org ID instead of the Group ID.

​
Available triggers

CoachIQ triggers fire in real time using webhooks. The Zap must be turned ON to receive events — events don’t queue up while a Zap is off, and they don’t backfill past activity. The Test trigger button in Zapier pulls a sample record for building purposes only; real automation starts when you publish and turn the Zap on. Two things to know about trigger data:
  • Guest submissions and anonymous purchases: for New Form and New Purchase, the submitter or buyer may not be a logged-in user. In those cases, user fields (email, phone, name) come through empty. Build your Zap to handle this — don’t assume user data is always present.
  • Money values are text, not numbers: purchase amounts come through as strings like "49.99". If a later step needs to do math, add a Zapier Formatter step to convert them.

​
Available actions

Use these to create records or send messages inside CoachIQ from an external trigger. A note on the “From Email” field: this sets who the message appears to be from in the athlete’s inbox. It must be the email address of an admin in your group. If you leave it blank, CoachIQ sends from your most-recently-created admin automatically.

​
Common use cases

​
Worked examples

​
New athlete → send a welcome in-app message

  1. Trigger: CoachIQ → New User. Connect your account, click Test trigger to pull a sample.
  2. Action: CoachIQ → Send an In-App Message.
    • Email: map the Email field from the New User trigger.
    • Message: Welcome! Reply here any time you have a question.
    • From Email (optional): your admin email address.
  3. Click Test — you should see In-App message sent! in the response.
  4. Click Publish, then toggle the Zap On.

​
New form submission → text yourself

  1. Trigger: CoachIQ → New Form. Test it to pull a recent submission.
  2. Action: CoachIQ → Send an SMS Message.
    • Phone: type your own phone number directly — this alert goes to you, not the submitter.
    • Message: New intake form just came in. (keep it under 160 characters).
  3. Test, confirm SMS sent!, then turn the Zap On.
Because forms can be submitted by guests with no email on file, send this alert to your own number rather than mapping the submitter’s contact info.

​
External lead form → add athlete to CoachIQ

  1. Trigger: your other app (e.g. Google Sheets → New Spreadsheet Row or Typeform → New Submission). Test it.
  2. Action: CoachIQ → Create User.
    • Email (required): map the lead’s email from your trigger.
    • First Name / Last Name / Phone: map them if you have them (all optional).
  3. Test — you’ll see the athlete’s record returned. If that email is already in your group, CoachIQ returns the existing athlete instead of creating a duplicate. That’s expected behavior.
  4. Turn the Zap On.
The CoachIQ integration is private and won’t show up in Zapier’s public app directory. Open the private invite link, accept it, and CoachIQ will be available when building Zaps.
This almost always means the wrong value was pasted into one of the fields. The most common cause: copying the Org ID instead of the Group ID from the API Keys page — they sit next to each other with similar-looking copy buttons.Re-open Settings → Developer → API Keys, copy the Group ID specifically, then reconnect in Zapier.
A real CoachIQ API Key is 128 characters. If Zapier rejects it for being too short, you likely pasted a partial key. Re-copy the full key from CoachIQ. If you can no longer see the key (it’s shown only once), create a + New API Key and use the new one.
Check these in order:
  1. Is the Zap turned ON? CoachIQ triggers only deliver events to Zaps that are actively on. A Zap in draft or toggled off won’t receive anything.
  2. Did the event happen after you turned it on? Triggers fire on new events going forward — they don’t backfill past activity.
  3. Did the right event occur? A New Form Zap only fires on form submissions, New Booking only on bookings, etc.
  4. Check Zapier’s Zap History. Open the Zap and look at its run history to see if it received the event and whether a later step errored.
This is not a failure. When you use Create User and that email already exists in your group, CoachIQ returns the existing athlete’s record instead of creating a duplicate. Your later steps still have a user to work with — just let it pass through.
SMS messages are capped at 600 characters. If you’re hitting that limit, shorten the message. For the most reliable delivery, keep texts to 160 characters or fewer — that’s a single text segment. If you need to send more text, use Send an In-App Message or Send an Announcement instead (both allow up to 15,000 characters).
Yes — one API Key can authenticate any number of Zaps. If you want the ability to revoke access to a specific Zap without affecting others, create a separate key for each integration.
Each Zapier connection is tied to one Group ID and API Key pair. To work with multiple groups, add a separate CoachIQ connection in Zapier for each one, using that group’s own Group ID and key. Name them clearly (e.g. “CoachIQ — East Location”) so you can pick the right one per Zap.

What are automations?

Build automated workflows entirely inside CoachIQ

Triggers and actions reference

Full reference for every CoachIQ automation trigger and action

API Keys

Find your Group ID and generate API keys

Webhooks

Advanced integrations using custom webhook endpoints