Build it
What do you want BotMape and Calendly 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 BotMape and Calendly
Triggers and actions 3 triggers · 26 actions
Trigger
New Lead CapturedTriggers when a new lead is captured — either from a chat conversation or added manually.
Action
Add agentCreate a new AI agent with custom configuration and personality. POST /api/chatbots
Action
Add knowledge base entryAdd training content (FAQ, documentation, policies) to an AI agent; auto-embedded. POST /api/chatbots/:chatbotId/knowledge
Action
Create LeadCreates a new lead in your CRM. Use this to push leads from other tools into your CRM automatically.
Action
Delete knowledge base entryRemove a specific knowledge entry from an AI agent's training data. DELETE /api/chatbots/:chatbotId/knowledge/:knowledgeId
Action
Get agentRetrieve detailed information about a specific AI agent by ID. GET /api/chatbots/:id
Action
List agentsGet all AI agents owned by the authenticated user with their configurations. GET /api/chatbots
Action
List knowledge base entriesRetrieve all knowledge base entries that train an AI agent's responses. GET /api/chatbots/:chatbotId/knowledge
Action
Update agentUpdate an existing AI agent's configuration, personality, or appearance. PUT /api/chatbots/:id
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.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews