Build for free
Introducing Scheduler support for Nylas Agent Accounts

Introducing Scheduler support for Nylas Agent Accounts

• 4 min read
Jump to section
Author: Nick Barraclough
Nick Barraclough
Tags:
Jump to section

Today we’re launching Scheduler support for Agent Accounts. Any Agent Account can now host a booking page.

Three things this gives you:

  1. Scheduling pages for your Agent Accounts’ calendars, for things like field technicians, treatment room, and for your agent itself.
  2. Bookings that update themselves, so a reschedule or a cancellation reaches the calendar without your code doing the work.
  3. A mailbox on the same account, so the identity that sends the booking link is the identity that receives the reply.

Check out the quickstart guide here.

Every Agent Account has a calendar Scheduler can read

An Agent Account gives a scheduling page to everything: a contractor or field technician, a vaccination bay or a consultation room, a piece of equipment, or an agent your application provisioned an hour ago. Each one gets an account with a full calendar, and Scheduler now reads availability from it and writes bookings back to it.

If the participants are with other providers, like Google or Microsoft, they receive a full calendar invite just like any other scheduling page. When the guests RSVP, your Agent Account gets that update too.

Creating a configuration

Point the configuration call at the Agent Account’s grant:

curl --compressed --request POST \
  --url "https://api.us.nylas.com/v3/grants/<AGENT_ACCOUNT_GRANT_ID>/scheduling/configurations" \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer <NYLAS_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
    "requires_session_auth": false,
    "participants": [{
      "name": "Support Agent",
      "email": "support-agent@yourdomain.com",
      "is_organizer": true,
      "availability": {
        "calendar_ids": ["primary"]
      },
      "booking": {
        "calendar_id": "primary"
      }
    }],
    "availability": {
      "duration_minutes": 30
    },
    "event_booking": {
      "title": "Support call"
    }
  }'

The response returns a configuration_id. Pass it to the <nylas-scheduling> component to embed the booking flow in your product, or use the Nylas-hosted page if you only need a link to send. The booking.created webhook fires the moment a guest confirms, so your application can act on the booking straight away.

If a colleague is attending the meeting, add their connected grant to the same configuration and Scheduler will only offer slots when both are free. Scheduler takes either an email address or a grant_id in the participant field, so you can address the Agent Account however your application already stores it.

When the guest emails back instead

Plenty of people ignore the link and reply asking about Thursday. When the mailbox and the booking sit in different places, something has to reconcile them.

Here they’re one account. The reply arrives in the inbox holding the thread, the booking sits on the calendar attached to it, and your agent reads one and updates the other. Reschedules and cancellations route to that calendar, so what your application knows and what the guest sees stay in agreement.

Common use cases

Support platforms. An agent triages a ticket, decides a call would be faster, and sends a booking link from the address the ticket arrived on. The customer never leaves the thread, and if they reply instead of clicking, the reply lands in the same account that holds the booking.

Sales tools. An agent works the reply thread and sends the link the moment a prospect is ready, against the calendar of the rep who will take the call. The meeting is booked in the hour they answered rather than the next time someone works the queue.

Resource booking. A consultation room, a bay, a machine or a booth is a bookable resource with no person attached. Each one gets an account and a page of its own, so a venue running twelve rooms is running twelve calendars your app controls rather than one shared calendar everybody edits.

Recruiting. An agent sits in a collective configuration with the interview panel, so candidates book against the panel’s availability rather than trading messages about time zones. When someone needs to move, the agent handles it on the thread instead of the candidate waiting for a coordinator to confirm what they already chose.

Get started today

Scheduler support for Agent Accounts is live on all Nylas applications.

Want to try it out? Sign in to your Nylas account or create a free Sandbox account. Agent Accounts are included on the free tier, so you can build the whole flow before you pay for anything.

Explore the resources:

Related resources

Agent Accounts Use Cases
The AI transaction coordinator that keeps the closing on schedule

Getting a house from accepted offer to keys runs on email and calendar invites between…

• 7 min read
Read more
Agent Accounts Use Cases
The AI executive assistant that runs its own inbox and calendar

An assistant that works over email and calendar has to be reachable. It cannot borrow…

• 8 min read
Read more
Agent Accounts Use Cases
The AI recruiting agent that schedules its own interviews

Hiring happens in email until it lands on a calendar. An AI recruiting agent needs…

• 7 min read
Read more