Connect Altoviz and Doclift PDF

Both apps 36Altoviz 24Doclift PDF 12

• Trigger
  Contact

  Triggers when a contact is created, updated or deleted.

• Trigger
  Customer

  Triggers when a customer is created, updated or deleted.

• Trigger
  Product

  Triggers when a product is created, updated or deleted.

• Action
  Create Contact

  Creates a new contact.

• Action
  Create Customer Family

  Creates a new customer family.

• Action
  Create Draft Sales Invoice

  Creates a new draft sales invoice.

• Action
  Create Product Family

  Creates a new product family.

• Action
  Create Receipt

  Creates a new receipt.

• Action
  Create Sales Credit

  Creates a new sales credit.

• Action
  Create Sales Quote

  Creates a new sales quote.

• Action
  Create Supplier

  Creates a new supplier.

• Action
  Delete Contact

  Delete an existing contact.

• Action
  Delete Customer

  Delete an existing customer.

• Action
  Delete Receipt

  Delete an existing receipt.

• Action
  Delete Sales Credit

  Delete an existing sales credit.

• Action
  Delete Sales Invoice

  Delete an existing draft sales invoice.

• Action
  Delete Sales Quote

  Delete an existing sales quote.

• Action
  Delete Supplier

  Delete an existing supplier.

• Action
  Download Purchase Invoice

  Download a purchase invoice.

• Action
  Get Settings

  Returns the Altoviz account's application settings (company, accounting, sales, VAT, e-invoicing, emailing, general and social settings).

• Action
  Update Customer

  Update an existing customer.

• Action
  Update Product

  Update an existing product.

• Action
  Update Receipt

  Update an existing receipt.

• Action
  Update Supplier

  Update an existing supplier.

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