When expense report submitted in Workday, sync it to Calendly.
When an expense report is submitted in Workday, send a meeting link via Calendly to discuss reimbursement details.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Workday Explore Workday →
TriggersFires when a new employee is added in Workday.
Fires when a field on an employee's profile changes in Workday.
Fires when an employee is offboarded in Workday.
Fires when an employee requests time off in Workday.
Creates a new employee record in Workday.
Updates a field on an employee's record in Workday.
Syncs an employee's active/terminated status in Workday.
Approves or denies a time-off request in Workday.
Calendly Explore Calendly →
TriggersFires when a new booking or appointment is made in Calendly.
Fires when a booking in Calendly is changed or canceled.
Fires when a new customer books for the first time in Calendly.
Creates a new booking or appointment in Calendly.
Cancels or moves a booking in Calendly.
Creates or updates a customer record in Calendly.
Adds a booking from Calendly to a connected calendar.
Common questions
Can Knit build “When expense report submitted in Workday, sync it to Calendly.” between Workday and Calendly?
Yes — describe it in the box above and Knit's Integrations Agent researches Workday and Calendly's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.