Integration
Connect Aviation Safety Data to Calendly
When something happens in Aviation Safety Data, 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 Aviation Safety Data 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 Aviation Safety Data and Calendly
Triggers and actions 3 triggers · 31 actions
Trigger
New eventPoll for newly published aviation safety occurrences.
- Find drone sightings by state
Get FAA drone sighting reports for one US state.
- Find laser strikes by airport
Get FAA laser incidents reported near one airport.
- Find laser strikes by state
Get FAA laser incidents reported for one US state.
- Find wildlife strikes by airport
Get FAA wildlife strikes reported for one airport.
- Find wildlife strikes by species
Get FAA wildlife strikes reported for one species.
- Get aircraft family safety stats
Get merged safety statistics for an aircraft family.
- Get airport
Look up airport reference data by ICAO ident or IATA code.
- Get event
Get one aviation safety occurrence with its sources and narrative references.
- Get narrative
Get a narrative by its source and the authority's own case id.
- List drone sightings
List global FAA UAS (drone) sighting reports.
- List events
List aviation safety occurrences with cursor pagination.
- List laser strikes
List global FAA reported laser incident aggregates.
- List wildlife strikes
List global FAA wildlife strike aggregates.
Trigger
Canceled scheduled event (polling)Triggers when a scheduled event is canceled.
- New scheduled event (polling)
Triggers when a new scheduled event is created.
- Cancel scheduled event
Cancels a scheduled event with a specified reason for the cancellation.
- Create single-use scheduling link
Creates a single-use booking link that allows one person to schedule an event.
- Get current user
Returns the authenticated user's profile including name, email, timezone, and scheduling URL.
- Get event type
Returns details for the specified event type.
- Get invitee
Returns details about a specific invitee for a scheduled event.
- Get invitee next scheduled event
Gets the next scheduled event for the invitee specified by their email.
- Get scheduled event
Returns details about a specific scheduled event.
- Get user availability schedule
Returns details for the specified user availability schedule.
- List event invitees
Returns the list of invitees for a scheduled event, optionally filtered by status.
- List event type availability schedules
Returns the event type's availability schedules.
- List event types
Returns your calendar's event type templates, optionally filtered by scope and active status.
- List organization memberships
Returns all members of the connected Calendly organization (paginated). One record per membership: user_email, user_uri, user_name, role.
- List scheduled events
Returns scheduled events, filterable by scope, status, date range, and invitee email.
- List user availability schedules
Returns the user's availability schedules.
- List webhook subscriptions
Returns all webhook subscriptions for your organization.
- Mark invitee as no-show
Records that an invitee did not attend their scheduled event.
- Undo invitee no-show
Removes a no-show marking from an invitee.
- Update event type availability schedule
Replaces 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.