Automation library · Scheduling

Create a Calendly availability API endpoint

Started by another system calling it. It calls services over plain HTTP rather than through connectors. 9 steps: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 2Logic 4Service 3

The steps in the order they run, from what starts it.

  1. 1Webhook TriggerWebhookStarts it
  2. 2Set ConfigurationSetLogic
  3. 3Get Current UserHttp RequestService
  4. 4Extract User InfoSetLogic
  5. 5Get Event TypesHttp RequestService
  6. 6Select Event TypeSetLogic
  7. 7Get Available TimesHttp RequestService
  8. 8Format AvailabilitySetLogic
  9. 9Respond with AvailabilityRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
9
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.