Connect CalendarLink and Doclift PDF

Both apps 21CalendarLink 9Doclift PDF 12

• 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.

• Trigger
  New PDF Document Generated

  Webhook trigger for Doclift's async document-generation completion callback (POST .../webhooks/doclift, X-Doclift-Signature: sha256=hmac). Delivery URL is configured manually on the external application in the Doclift dashboard — no register/list/delete API exists. Fires once per document_request (all its documents_generations resolved to success/error), payload includes id, tag, type, timestamp, documents_generations[] (generation_status, file{filename,url,size}).

• Action
  Add Template

  create a custom (HTML-body) template: title, description, content, orientation, margins, optional variables_attributes. Server forces category=custom.

• Action
  Add Variable

  create a variable on a custom template: title (unique, naming pattern), description, field_type (text/checkbox/radio/select/collection, default text), seed_value, allowed_values.

• Action
  Delete Template

  removes a custom template (scope restricted to category=custom, non-archived, same org).

• Action
  Get Document Request

  status and documents_generations detail (signed file url, valid 2 hours) for one document request.

• Action
  Get Template

  full template detail including variables and content (custom templates); works for any published template of the three categories.

• Action
  List Document Requests

  list document generation requests with id, tag, type, status, documents_generations (each with generation_status and file url).

• Action
  List Templates

  returns published, non-archived templates (custom/fillable_form/workflow) for the organization: id, title, description.

• Action
  List Variables

  all variables of a custom, non-archived template: id, title, description, field_type, allowed_values (no pagination, no seed_value).

• Action
  Publish Template

  marks a custom template published (usable for document generation).

• Action
  Unpublish Template

  marks a custom template unpublished.

• Action
  Update Variable

  update description/field_type/allowed_values/title of a variable; allowed_values replaces the stored array.

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