[REQUEST] Add Calendly tools integration (event types & scheduled events)

[junaiddshaukat]

Is your feature request related to a problem? Please describe.

I’d like to build agent workflows in Sim that can understand and manage my scheduled meetings.
Right now, Sim integrates with many CRMs, calendars, and communication tools, but there is no first‑class Calendly integration, so agents can’t easily read upcoming events, fetch event details, or act on them (e.g. cancel/reschedule, send reminders).

---

Describe the solution you'd like

Add a dedicated Calendly tools integration under apps/sim/tools/calendly that exposes Calendly’s REST API as tools in workflows.

• Auth
  • Use Personal Access Token (PAT) for the first version.
  • Tools accept a Calendly token (user-only param) and call the API with:
    • Authorization: Bearer <token>
    • Calendly-API-Version: 2
• New tools
  • calendly_list_event_types
    • List event types for the authenticated user/org, returning name, slug, scheduling_url, duration, active/inactive, and identifiers.
  • calendly_list_scheduled_events
    • List scheduled events in a time range (min_start_time, max_start_time, optional status and pagination).
  • calendly_get_event
    • Fetch full details for a single scheduled event by ID (times, location, invitees, questions/answers, status).
  • calendly_cancel_event
    • Cancel a scheduled event with a reason string and return confirmation/updated status.

These tools would be registered in apps/sim/tools/registry.ts so they appear in the workflow editor, with parameters following the existing visibility system (user-only for the token, user-or-llm for filters and IDs).

---

Describe alternatives you've considered

• Using the generic HTTP tool to call Calendly’s API directly, but this requires manually handling auth headers, pagination, and response shaping in every workflow.
• Relying only on Google Calendar tools, but that doesn’t cover users and teams that standardize on Calendly links and workflows.

Both approaches are more error‑prone and significantly less user‑friendly than a dedicated Calendly integration with well‑typed params and normalized outputs.

---

Additional context

• Calendly API docs: Calendly API overview and Getting started.
• Example use cases this would unlock:
  • “Daily prep” agents that list today’s meetings and generate agendas or context summaries.
  • Post‑meeting summary workflows that pull event details and send follow‑up emails or Slack messages.
  • Automated cancellation / rescheduling flows that react to conflicts or other system signals.

I’m happy to implement this feature following the existing tools architecture and naming/visibility conventions if it’s accepted.

[junaiddshaukat]

@waleedlatif1 I want to work on this feature, if it looks good to you.Then you can assign this issue to me

[waleedlatif1]

@junaiddshaukat added in #2056