Connect CompanyHub and Doclift PDF

Both apps 25CompanyHub 13Doclift PDF 12

• Trigger
  New Company

  Triggers when a new company is added in CompanyHub.

• Trigger
  New Contact

  Triggers when a new contact is created in CompanyHub.

• Trigger
  New Deal

  Triggers when a new deal is created in CompanyHub.

• Trigger
  New Record (Custom Table)

  Triggers when a new record is added to the CompanyHub table you choose, such as one of your custom tables.

• Trigger
  New Task

  Triggers when a new task is created in CompanyHub.

• Trigger
  Record Updated

  Triggers when a record in the chosen CompanyHub table is created or changed.

• Action
  Create a Record (Custom Table)

  Creates a record in any CompanyHub table, including custom tables, from the field values you supply, and returns the new record's ID.

• Action
  Create Company

  Creates a new company record in CompanyHub and returns its ID.

• Action
  Create Contact

  Creates a contact in CompanyHub and returns the new contact's ID.

• Action
  Create Deal

  Creates a deal in CompanyHub and returns the new deal's ID.

• Action
  Create Task

  Creates a task in CompanyHub with the given title, type, category, assignee and end time, plus any other Task fields you set.

• Action
  Find Record

  Returns the records in a CompanyHub table (Contact, Company, Deal or a custom table) whose chosen field matches the value you supply.

• Action
  Update Record

  Updates an existing record in a CompanyHub table (Contact, Company, Deal or a custom table), changing only the fields you supply.

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