Connect Doclift PDF to Emelia

Both apps 28Doclift PDF 12Emelia 16

• 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
  Add campaign

  Creates a new email campaign in Emelia with the given name and time zone.

• Action
  Add Contact to a Campaign

  Adds a contact to an Emelia campaign.

• Action
  Add Contact to a List

  Adds a single contact to an Emelia list (and to any campaigns using that list), optionally updating it if it already exists.

• Action
  Add Contact to Blacklist

  Adds an email address or an entire domain to your Emelia blacklist so it is never contacted by your campaigns.

• Action
  Add list

  Creates a new, empty contact list in Emelia.

• Action
  Delete contact

  Deletes a contact (and its company data) from an Emelia contact list; the removal also propagates to campaigns using that list.

• Action
  Get campaign

  Returns the full configuration of an Emelia campaign, including the contact lists attached to it and excluded from it.

• Action
  Get campaign statistics

  Returns sending, open, click and reply statistics for an Emelia campaign, overall and per step.

• Action
  Get contact

  Returns a single contact from an Emelia contact list.

• Action
  List Campaign Contacts

  Returns the contacts enrolled in an email campaign, optionally filtered by an engagement event or a search term.

• Action
  List campaigns

  Returns all campaigns in your Emelia account.

• Action
  List contacts

  Returns the contacts in an Emelia contact list, optionally filtered by search text or an exact email or LinkedIn URL.

• Action
  Search Contact

  Searches a contact list for contacts by exact email, LinkedIn URL, or free text, and returns the matches.

• Action
  Set a Custom Field to a Contact

  Sets the value of a custom field on a contact in an Emelia campaign, identified by email or LinkedIn profile URL.

• Action
  Test Webhook

  Sends a test call to an existing Emelia webhook.

• Action
  Update contact

  Updates an Emelia contact's values; fields you don't send stay unchanged, and changes propagate to campaigns using the contact's list.

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