Connect Cisco WebEx and Doclift PDF

Both apps 24Cisco WebEx 12Doclift PDF 12

• Trigger
  New meeting

  Fires when a meeting is created. Webhook resource=meetings event=created

• Trigger
  New message

  Fires when a message is created in a space.

• Action
  Add meeting

  Schedules a new Webex meeting (or webinar / personal room meeting) and returns the created meeting.

• Action
  Add message

  Posts a plain-text or Markdown message, optionally with one file or one card, to a Webex space or directly to a person.

• Action
  Add room

  Creates a Webex space (room). The connected user is automatically added as a member.

• Action
  Delete meeting

  Deletes a scheduled meeting or an entire meeting series. A deleted meeting cannot be recovered.

• Action
  Find people by criteria

  Returns up to 100 people in the Webex organization that match the specified email, name, IDs, roles or location.

• Action
  Get meeting

  Retrieves the details of a Webex meeting series, scheduled meeting or meeting instance by its id.

• Action
  Get membership

  Returns one space membership: who the member is, which space, and whether they moderate it.

• Action
  List messages

  Lists the messages in a Webex space, newest first. Optionally narrow to replies in one thread, messages mentioning you, or messages sent before a date or message.

• Action
  List rooms

  List the Webex spaces (rooms) the connected user belongs to, optionally filtered by team or type.

• Action
  Update meeting

  Updates a meeting series or a single scheduled meeting in Webex. Only the fields you fill in are changed.

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