Customer Onboarding Drip, Run by an Agent A developer built a customer onboarding automation system using Nylas APIs that treats onboarding as a state machine driven by engagement signals. The system uses tracked welcome emails, self-service booking links, and webhooks to automatically move customers through stages like engaged, unresponsive, and kickoff booked without manual intervention. The tutorial also highlights the use of Nylas Agent Accounts for dedicated sending identities and Scheduler Configurations for zero-frontend booking pages. How many of the customers you onboarded last month actually booked the kickoff call you emailed them about? If you can't answer that without checking a spreadsheet someone updates by hand, your onboarding sequence is running on hope. The fix is to treat onboarding as a state machine driven by real engagement signals: a welcome email with open and click tracking, a self-service booking link for the kickoff, and webhooks that move each customer between states — engaged, unresponsive, kickoff booked — without anyone watching an inbox. The full recipe is in the customer onboarding automation tutorial https://developer.nylas.com/docs/cookbook/use-cases/automate/automate-customer-onboarding/ , and the whole thing gets more interesting when the sending mailbox is an Agent Account https://developer.nylas.com/docs/v3/agent-accounts/ in beta — a dedicated onboarding@ address your app owns, so replies route back to the same identity that sent the drip. The first send carries tracking options so you learn whether the customer opened it and what they clicked. The label field is the trick: it encodes which customer and which stage the event belongs to, so webhook handlers don't need a lookup table. curl --request POST \ --url 'https://api.us.nylas.com/v3/grants/