Automation library · Scheduling

Send smart lock PINs for Apaleo reservations with Seam

Started by a clock, and works across Gmail and Twilio. 11 steps: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 1Service 8

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

  1. 1When Triggered Every 58 MinutesSchedule triggerStarts it
  2. 2On Reservation Unit AssignmentApaleo triggerStarts it
  3. 3Obtain Apaleo Access TokenHttp RequestService
  4. 4Retrieve Reservation DetailsApaleoService
  5. 5Update API Credential InformationHttp RequestService
  6. 6Link Room to Lock CodeCodeLogic
  7. 7Create Access Code on SeamHttp RequestService
  8. 8Add PIN to Reservation NoteApaleoService
  9. 9Retrieve Customer Contact InfoHttp RequestService
  10. 10Deliver PIN via GmailGmailService
  11. 11Send PIN using TwilioTwilioService

How it's built

Starts on
A clock
Steps
11
Size
Medium: a working afternoon
Connects to
Gmail, Twilio
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail and Twilio accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

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. 11 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 11 steps before you point it at anything that matters.