Connect Make.com or n8n

Kooday ships no calendar or CRM connectors of its own. Instead it gives your own Make.com or n8n scenario two things: the events you choose, sent out as they happen, and a private address that scenario can call back on. What sits in between — the Google Calendar step, the CRM step — is yours, so you are never waiting on us to support a tool you already pay for.

The wizard removes the fiddly half of that. It creates the inbound address, the outbound connector and the event routing together, and hands you a workflow file with the callback address and the events already wired in.

Two steps stay manual, because both need access to accounts only you hold: authorizing Google Calendar inside Make.com or n8n, and activating its webhook so it gives you a URL. That URL is the one thing you paste back.

The five-minute setup

1. Open Integrations in the dashboard.
2. Under Connect an automation platform, choose Make.com or n8n.
3. Tick the events this workflow should receive. Nothing is ticked for you.
4. Turn on Allow booking metadata write-back only if the workflow will send calendar details back onto a booking.
5. Choose Generate template, then Copy template JSON.
6. Import that JSON into Make.com or n8n. Work through the steps it marks for you: authorize Google Calendar, and — if you turned on write-back — add the signature to the callback step.
7. Activate the workflow’s webhook, paste the URL it gives you into Automation webhook URL, and choose Save and test.

⚠️ Your connector stays switched off until you finish step 7. That is deliberate: until it has a real URL there is nowhere to deliver to, and queuing failed deliveries against a dead address would pause the connector just as you started using it.

The signing secret

Turning on write-back creates a private address your workflow calls back on, and a secret it signs those calls with.

The address is already in the JSON you copy. The secret is not, and that is deliberate: signing is a step you add yourself, because the way to compute it differs between Make.com and n8n versions, and a wrong one imports cleanly and then fails every call. The workflow marks the spot, and the wizard shows the secret beside the template with a copy button.

⚠️ The secret is shown once and cannot be read back afterwards. Nothing in the dashboard will show it to you again.

If you lose it, generate a new template and use that one instead. Then open the Integrations list and delete the connector the first run created, or the same event will be sent to both — removing the connector removes its event routing with it.

The old callback address stays live, and there is no screen for switching it off yet. Ask us to retire it if the secret went somewhere it should not have.

Treat the secret like a password: anyone holding it can add calendar details to a booking in your workspace. That is the whole of what the address accepts, and it is why write-back is the only setting that creates one — with write-back off there is no callback address and no secret at all, because the workflow only listens.

Choose the events

The checklist is your workspace’s routable events. It is opt-in, one workflow at a time: for a calendar scenario, tick the booking events your workflow actually handles and leave the rest clear. Every event you tick is one your scenario has to have a branch for.

Each run of the wizard creates its own connector, address and routing. Running it again does not rewrite a workflow you already set up, so you can build a second scenario for a different job without touching the first.

Allow booking write-back

Leave this off when the workflow only reports what it did. With it on, the callback may add calendar details — the event’s id, and a link to it — onto the booking that triggered it.

It cannot do anything else to that booking. Confirming, cancelling and rescheduling stay with your assistant and your team, and a callback that tries to set a booking’s status or move its time is refused outright rather than partly applied.

Make.com

Import the copied JSON as a scenario blueprint. Each module carries a note saying what it still needs.

Open the Google Calendar module, connect your account and pick the calendar you want events written to. If you turned on write-back, open the HTTP module and fill in the two signature headers it marks. Then open the Custom Webhook module, activate it, and copy the address Make.com shows you.

n8n

Import the copied JSON as a workflow. Each node carries a note saying what it still needs.

Select your Google Calendar credential on the Google Calendar node. If you turned on write-back, open the Kooday callback node and fill in the two signature headers it marks. Then activate the workflow and copy the Production URL from its Webhook node.

Troubleshooting

The Generate template button is greyed out

Tick at least one event. The wizard will not build an every-event workflow for you.

My callback is rejected with 401

The signature header is missing or wrong. Kooday signs and expects sha256= followed by an HMAC of {timestamp}.{body} using your signing secret, and the timestamp header must be the same value you signed. The workflow marks the two headers that need it; your developer will want the integration recipes.

The test failed after I pasted the URL

Check the workflow is activated in Make.com or n8n and that you pasted the URL from its live webhook rather than its test one. Paste it again and choose Save and test — that saves the address and switches the connector on in one step.

Events are not arriving

Open the connector in the Integrations list. If it is switched off, the paste-back step did not complete: paste the URL and choose Save and test again.

My booking status did not change

That is expected. Write-back adds calendar details to a booking; it never confirms, cancels or reschedules one. Those are separate actions in Kooday.

Keeping your knowledge base in step

Kooday can also take knowledge-base content over a callback address, so a CMS or docs system keeps your assistant current instead of somebody re-pasting pages by hand.

That needs its OWN address, not the one this wizard creates: an address does exactly one job, and the wizard’s job is adding calendar details to a booking. Ask us to set a knowledge-push address up for you — the wizard does not offer it yet.

Anything pushed that way lands in the review queue, exactly like the suggestions your assistant raises itself — it never goes live unread. Pushing the same unchanged page again does nothing, so a nightly sync is safe.

This one is not in the wizard yet: it needs a webhook set up through the API. Your developer will want the integration recipes.

Related

• Connecting your own systems — the manual route, and the one to use for Zapier or your own backend. It also covers testing a connector, watching deliveries and reading a failure.
• Which events you can send — every event name, and what each one carries.