Build it
What do you want Calendly and Wachete to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Calendly and Wachete
Triggers and actions 4 triggers ยท 25 actions
Trigger
Canceled scheduled event (polling)Triggers when a scheduled event is canceled.
Trigger
New scheduled event (polling)Triggers when a new scheduled event is created.
Action
Cancel scheduled eventCancels a scheduled event with a specified reason for the cancellation.
Action
Create single-use scheduling linkCreates a single-use booking link that allows one person to schedule an event.
Action
Get current userReturns the authenticated user's profile including name, email, timezone, and scheduling URL.
Action
Get event typeReturns details for the specified event type.
Action
Get inviteeReturns details about a specific invitee for a scheduled event.
Action
Get invitee next scheduled eventGets the next scheduled event for the invitee specified by their email.
Action
Get scheduled eventReturns details about a specific scheduled event.
Action
Get user availability scheduleReturns details for the specified user availability schedule.
Action
List event inviteesReturns the list of invitees for a scheduled event, optionally filtered by status.
Action
List event type availability schedulesReturns the event type's availability schedules.
Action
List event typesReturns your calendar's event type templates, optionally filtered by scope and active status.
Action
List organization membershipsReturns all members of the connected Calendly organization (paginated). One record per membership: user_email, user_uri, user_name, role.
Action
List scheduled eventsReturns scheduled events, filterable by scope, status, date range, and invitee email.
Action
List user availability schedulesReturns the user's availability schedules.
Action
List webhook subscriptionsReturns all webhook subscriptions for your organization.
Action
Mark invitee as no-showRecords that an invitee did not attend their scheduled event.
Action
Undo invitee no-showRemoves a no-show marking from an invitee.
Action
Update event type availability scheduleReplaces a single host's availability schedule on a Calendly event type with explicit date rules (full overwrite). Built for CalendarConnect: push real Mindbody bookable slots into Calendly so only MBO-bookable times are offered. CRITICAL: the host is targeted by the NESTED availability_rule.user โ a top-level user alone is silently ignored and Calendly replaces the OAuth token owner's schedule instead. Always verify stored_user equals the requested host before trusting the result. For round-robin events, call once per host.
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange the settings of an existing Wachete monitor โ name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value โ including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.