Connect Doclift PDF to Avoma

Both apps 24Doclift PDF 12Avoma 12

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

• Action
  Get call

  Returns a single Avoma call by its external ID, including its CRM links, recording URL, processing state and linked meeting.

• Action
  Get meeting

  Returns a single Avoma meeting by its UUID, including its attendees, schedule, state, and recording and transcription details.

• Action
  Get meeting insights

  Returns the AI notes, keyword occurrences, popular keywords and speakers for a completed Avoma meeting.

• Action
  Get recording

  Returns the signed audio and video download links for the recording of an Avoma meeting. If the video is still being processed, returns a message instead of the links.

• Action
  Get transcription

  Returns the transcript of a meeting's recording, including the speakers, the timed transcript text and a link to the VTT file.

• Action
  List calls

  Returns the calls in your Avoma organization that started within a date range, optionally narrowed to inbound or outbound calls.

• Action
  List meetings

  Returns the meetings in your Avoma organization that started within a date range, optionally filtered by attendee, CRM record, recording length or meeting type.

• Action
  List notes

  Returns the AI-generated notes for meetings in a date range, optionally narrowed to one meeting or custom category.

• Action
  List scorecard evaluations

  Returns completed scorecard evaluations for meetings, optionally narrowed by date range, scorecard template, meeting or evaluated user.

• Action
  List users

  Returns the users in your Avoma organization, including each user's name, email, role, teams and status.

• Action
  Update call

  Updates an existing call's details in Avoma, such as its subject, participant names, meeting purpose and outcome, or linked CRM records, and returns the updated call.

• Action
  Upload Audio Call

  Creates a call in Avoma from a publicly reachable audio recording. Avoma downloads the recording and processes it into a transcript and notes, or uses a transcript you supply.

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