Integration
Connect Expiration Reminder to Calendly
When something happens in Expiration Reminder, your agent does the next thing in Calendly. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Expiration Reminder 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 Expiration Reminder and Calendly
Triggers and actions 5 triggers · 33 actions
Trigger
New ContactTriggered when a new contact is added to your Expiration Reminder account.
Trigger
New Expiration ItemTriggered when a new expiration item is added to your Expiration Reminder account.
Trigger
Status Changed Expiration ItemTriggered when an expiration item's status changes in Expiration Reminder — for example when it moves from active to expiring or expired.
Action
Add LocationCreates a location in Expiration Reminder, optionally nested under a parent location and assigned to a team. Any custom fields defined on locations in your account can be set too. Returns the created location.
Action
Create ContactCreates a contact in Expiration Reminder with their email, contact details, type, location and team, plus any custom fields defined on contacts in your account. Returns the created contact.
Action
Create Expiration ItemCreates an expiration item in Expiration Reminder with its name and expiration date, optionally attaching contacts, locations, tags, a category and an assignee, plus any custom fields defined in your account. Returns the created item.
Action
Create Expiration Item for ContactCreates an expiration item in Expiration Reminder and attaches it to a specific contact, with its name, expiration date and category, plus any custom fields defined in your account. Returns the created item.
Action
Delete ContactDeletes a contact from Expiration Reminder. Returns the contact record that was deleted.
Action
Delete Expiration ItemDeletes an expiration item from Expiration Reminder. Returns the item record after deletion.
Action
Find ContactReturns the Expiration Reminder contacts matching a search term or an exact email address, with the total number of matches.
Action
Find ExpirationReturns the Expiration Reminder expiration items matching a search term and status, with the total number of matches.
Action
Get ContactReturns a single Expiration Reminder contact by its id, including their contact details, assignment, location and every custom field stored on them.
Action
Get Expiration ItemReturns a single Expiration Reminder expiration item by its id, including its category, contacts, locations, tags, attachments and every custom field stored on it.
Action
List ContactsReturns the contacts in your Expiration Reminder account, with the total number of contacts.
Action
List Expiration ItemsReturns the expiration items in your Expiration Reminder account, optionally limited to one status, with the total number of items.
Action
List LocationsReturns the locations in your Expiration Reminder account, with the total number of locations.
Action
Renew ExpirationRenews an Expiration Reminder expiration item by moving it to a new expiration date. Returns the renewed item.
Action
Update Expiration ItemUpdates an existing Expiration Reminder expiration item. Fields you leave blank are left unchanged; custom fields defined in your account can be set too. Returns the updated item.
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.