Connect Campaign Monitor and Doclift PDF

Both apps 30Campaign Monitor 18Doclift PDF 12

• Trigger
  New client

  Polling trigger. Fires when a new client is added to the account.

• Trigger
  New list

  Polling trigger. Fires when a new list is added to the specified client.

• Trigger
  New subscriber

  Polling trigger. Fires when a new active subscriber is added to the specified list.

• Action
  Add campaign

  Create a draft campaign.

• Action
  Add or update subscriber

  Adds a subscriber to the specified list if the email is not found, otherwise updates the existing subscriber.

• Action
  Create list

  Creates a new subscriber list for the specified client.

• Action
  Delete list

  Delete a list.

• Action
  Delete subscriber

  Delete a subscriber from a list.

• Action
  Get list

  Get details of a list.

• Action
  Get subscriber

  Retrieves a subscriber's details (including custom fields and state) by email from the specified list.

• Action
  List campaigns

  List sent campaigns for a client.

• Action
  List draft campaigns

  Lists a client's draft (unsent) campaigns.

• Action
  List lists

  List all subscriber lists for a client.

• Action
  List segments

  List segments for a list.

• Action
  List subscribers

  List active subscribers of a list (paginated).

• Action
  Unsubscribe

  Removes a subscriber from the specified list.

• Action
  Update list

  Update list settings.

• Action
  Update subscriber multi-select field

  Updates a subscriber's multi-select custom field. Existing selected values can be retained or replaced.

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