Connect Direct Mail and Doclift PDF

Both apps 24Direct Mail 12Doclift PDF 12

• Trigger
  New Contact

  Triggers when a new contact is added to a Direct Mail address group.

• Trigger
  Sent Campaign

  Triggers when an email campaign is sent from a Direct Mail project (a new campaign report appears).

• Trigger
  Updated Contact

  Triggers when a contact in a Direct Mail address group is added or changes, including being unsubscribed or hard bounced.

• Action
  Add or Update Contact

  Adds a contact to a Direct Mail address group; Direct Mail merges it with an existing contact that has the same email address.

• Action
  Delete Contact

  Removes the contact with the given email address from a Direct Mail address group.

• Action
  Find Contact

  Finds a contact in a Direct Mail address group by email address.

• Action
  Get report

  Returns a campaign report from a Direct Mail project, including its delivery statistics and links to recipients, opens and clicks.

• Action
  List address groups

  Returns every address group (mailing list) in a Direct Mail project, with its name, UUID, blacklist flag and address count.

• Action
  List projects

  Returns every Direct Mail project your API key has been granted access to.

• Action
  List reports

  Returns the campaign reports in a Direct Mail project, with send date, status and open, click, bounce and unsubscribe counts.

• Action
  Unsubscribe Contact

  Marks the contact with the given email address as unsubscribed in a Direct Mail address group.

• Action
  Update Contact

  Updates the contact with the given email address in a Direct Mail address group.

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