Connect CalendarLink to Reepay

Both apps 29CalendarLink 9Reepay 20

• Trigger
  New Upcoming Event

  Triggered when a new upcoming event is added to your CalendarLink organisation.

• Action
  Create New Event

  Creates an event in a CalendarLink collection and returns its add-to-calendar link. Times use the format 2026-09-01 09:00:00. Optionally turns on RSVP with a deadline, attendee limit and notification settings.

• Action
  Find Event

  Searches your CalendarLink events for one whose title contains the text you give, and returns the first match with its add-to-calendar link, times and RSVP counts.

• Action
  List Contacts

  Returns a page of the contacts in your CalendarLink organisation, 15 per page, along with how many pages there are.

• Action
  List Event Collections

  Returns every event collection in your CalendarLink organisation, with each collection's ID, name, description, public link and event count.

• Action
  List Event Registrations

  Returns a page of the people who signed up for one CalendarLink event, 15 per page. The event must have RSVP turned on.

• Action
  List Past Events

  Returns a page of your CalendarLink events that have already finished, 15 per page, newest first.

• Action
  List Upcoming Events

  Returns a page of your CalendarLink events that have not happened yet, 15 per page.

• Action
  Update Event Collection

  Changes the settings of one CalendarLink event collection — its name, description, appearance, what visitors can add and whether sign-up is required. Only the fields you fill in are changed; the rest keep their current values.

• Action
  Add coupon

  Create a new coupon. POST /v1/coupon

• Action
  Add credit

  Create a credit note/credit for a customer. POST /v1/credit

• Action
  Add customer

  Create a new customer. POST /v1/customer

• Action
  Add invoice

  Create an invoice for a customer. POST /v1/customer/{handle}/invoice

• Action
  Add plan

  Create a new subscription plan. POST /v1/plan

• Action
  Add subscription

  Create a new subscription for a customer. POST /v1/subscription

• Action
  Cancel subscription

  Cancel a subscription by handle. POST /v1/subscription/{handle}/cancel

• Action
  Delete customer

  Delete a customer by handle. DELETE /v1/customer/{handle}

• Action
  Get charge

  Retrieve a charge by handle. GET /v1/charge/{handle}

• Action
  Get coupon

  Retrieve a coupon by handle. GET /v1/coupon/{handle}

• Action
  Get customer

  Retrieve a customer by handle. GET /v1/customer/{handle}

• Action
  Get invoice

  Retrieve an invoice by id. GET /v1/invoice/{id}

• Action
  Get plan

  Retrieve the current version of a plan by handle. GET /v1/plan/{handle}/current

• Action
  Get subscription

  Retrieve a subscription by handle. GET /v1/subscription/{handle}

• Action
  List customers

  List all customers. GET /v1/list/customer

• Action
  List invoices

  List all invoices. GET /v1/list/invoice

• Action
  List plans

  List all plans. GET /v1/list/plan

• Action
  List subscriptions

  List all subscriptions. GET /v1/list/subscription

• Action
  Update customer

  Update an existing customer by handle. PUT /v1/customer/{handle}

• Action
  Update subscription

  Change/update an existing subscription by handle. PUT /v1/subscription/{handle}

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.