Connect Callingly and Doclift PDF

Both apps 28Callingly 16Doclift PDF 12

• Trigger
  Call Completed

  Triggers when a call to a lead is made and completes in Callingly.

• Trigger
  Lead Created

  Triggers when a new lead is added to Callingly.

• Trigger
  Lead Updated or Tagged

  Triggers when a Callingly lead is tagged or its status, stage or result changes.

• Trigger
  New SMS

  Triggers when a text message is sent or received in Callingly.

• Action
  Call Lead

  Creates or updates a lead and immediately calls your team, connecting the first rep who answers to the lead.

• Action
  Delete Lead

  Deletes a Callingly lead.

• Action
  Find Lead

  Finds a Callingly lead by phone number and returns the first match.

• Action
  Get Call

  Returns one Callingly call by its ID, with its outcome, duration, recording and transcript.

• Action
  Get Lead

  Returns one Callingly lead by its ID, with its contact details and status.

• Action
  List Sequences

  Returns the follow-up sequences in the Callingly account.

• Action
  List Teams

  Returns the teams in the Callingly account.

• Action
  List Users

  Returns the users (agents) in the Callingly account.

• Action
  Schedule Call

  Creates or updates a lead and schedules a call from your team to the lead at the time you choose.

• Action
  Schedule SMS

  Schedules a text message to an existing Callingly lead for a future time.

• Action
  Send SMS

  Sends a text message from one of your Callingly numbers to a lead.

• Action
  Update or Tag Lead

  Updates a Callingly lead's details, status, stage or tags.

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