Connect Brevo and Doclift PDF

Both apps 43Brevo 31Doclift PDF 12

• Trigger
  Company Added

  Triggers when a company is created in Brevo.

• Trigger
  Company Updated

  Triggers when a company is updated in Brevo.

• Trigger
  Contact Added

  Triggers when a Brevo contact is added.

• Trigger
  Contact Subscribed to List (instant)

  Instant trigger — fires when a contact is added to a list (Brevo marketing webhook event listAddition). Self-registering via the Brevo Create/Delete webhook API.

• Trigger
  Contact Unsubscribed

  Triggers when a contact unsubscribes from an email campaign in Brevo.

• Trigger
  Contact Updated (instant)

  Instant trigger — fires when a contact is updated (Brevo marketing webhook event contactUpdated). Self-registering via the Brevo Create/Delete webhook API.

• Trigger
  Deal Added

  Triggers when a deal is created in Brevo.

• Trigger
  Deal Stage Updated

  Triggers when a deal's stage is updated in Brevo.

• Trigger
  Link Clicked

  Triggers when a Brevo contact clicks on any link in a Brevo email campaign.

• Trigger
  Marketing Email Delivered

  Triggers when a Brevo campaign marketing email is delivered.

• Trigger
  Marketing Email Hard Bounced

  Triggers when a Brevo campaign marketing email is hard bounced.

• Trigger
  Marketing Email Opened

  Triggers when a Brevo campaign marketing email is opened.

• Trigger
  New Campaign Status

  Triggers when the status of a Brevo campaign is updated.

• Trigger
  Transactional Email Delivered

  Triggers when a Brevo transactional email is delivered.

• Trigger
  Transactional Email Hard Bounced

  Triggers when a Brevo transactional email is hard bounced.

• Trigger
  Transactional Email Opened

  Triggers when a Brevo transactional email is opened.

• Action
  Add or Update Associations

  Adds or updates associations to companies, deals or contacts in Brevo.

• Action
  Add or Update Company

  Create a new company or update an existing one in Brevo.

• Action
  Add or Update Contact

  Creates or updates a contact. An attribute you map but leave EMPTY is IGNORED - the stored value is preserved, not deleted. Because of that, this action cannot CLEAR an attribute: to empty one, edit it in Brevo directly. Note an explicit null does not clear on Brevo either.

• Action
  Add or Update Deal

  Create a new deal or update an existing one in Brevo.

• Action
  Delete Company

  Deletes the selected company in Brevo, identified by its company ID.

• Action
  Delete Contact

  Deletes the selected contact in Brevo. The contact can be identified by its email address or its contact ID.

• Action
  Delete Deal

  Deletes the selected deal in Brevo, identified by its deal ID.

• Action
  Event Create

  Create event for selected contact.

• Action
  Find Company

  Finds companies in Brevo whose name matches the name you supply. Returns every match, up to 50.

• Action
  Find Deal

  Finds deals in Brevo whose name matches the name you supply. Returns every match, up to 50.

• Action
  Remove Associations

  Removes associations between companies, deals, or contacts in Brevo.

• Action
  Search Contact

  Check if a contact exists in Brevo and fetch the contact details. Contact can be found by email, mobile phone number, Brevo contact ID, external ID, Whatsapp ID and landline number.

• Action
  Send Transactional Email

  Sends an email from your Brevo account with HTML or plain text content.

• Action
  Send Transactional SMS

  Sends an transactional SMS from your Brevo account.

• Action
  Unsubscribe Contact

  Unsubscribe contact from the list(s) he belong to.

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