This template starts when a Calendly invitee is created, maps name, email, and event in JavaScript, and creates a Dubsado project through the Dubsado API. Connect Calendly and point the trigger at the event type you want. Put the Dubsado API key in the JavaScript node.
Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.
Full pricing — how CPU seconds work →Workflow preview
The scenario starts when someone books the Calendly event type you choose.
JavaScript sends invitee name, email, and event details to the Dubsado API. Put the Dubsado API key in that JavaScript node.
Add a Calendly connection. Add a trigger for a new invitee and select the event type that should open a Dubsado project.
Add a JavaScript node and put your Dubsado API key there.
In JavaScript, map invitee name, email, and event onto the Dubsado project payload. Match on email when Dubsado already has the client. Book a test event and confirm the project appears in Dubsado.
FAQ
More templates
This template watches a Gmail label for messages that should become calendar events. ChatGPT reads the subject and body and returns title, start, end, and location. Google Calendar creates the event on the calendar you connect. Connect Gmail and Google Calendar, then point the trigger at the label you use for reservations and meetings.
This template starts when a Google Calendar event ends, computes minutes from the start and end times, and logs that duration in Teamwork. Put a task or project id in the event description, or set a default on the Teamwork step. Connect Google Calendar and Teamwork, then point the trigger at the calendar you track.
This template watches Toggl Track for new or stopped time entries, maps project, description, start, and stop in JavaScript, and writes a Google Calendar event with that window. Repeat updates from the same Toggl id refresh the same event instead of duplicating it. Connect Toggl Track and Google Calendar. Put the Toggl API token on the Toggl connection.
