Connect Doclift PDF and Halo Service Solutions

Both apps 28Doclift PDF 12Halo Service Solutions 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.

• Trigger
  New Ticket

  Triggers when a new ticket is logged in Halo.

• Trigger
  Ticket Updated

  Triggers when a ticket is created or updated in Halo.

• Action
  Add action to ticket

  Adds a new action (note, update or outcome) to an existing Halo ticket.

• Action
  Add project

  Creates a new project in Halo and returns the created project record.

• Action
  Create Site

  Creates a new site for a customer in Halo.

• Action
  Create Ticket

  Creates a new ticket in Halo with a summary, description and optional customer, user, type, priority, status and assignment.

• Action
  Create User

  Creates a new end user in Halo under the chosen site.

• Action
  Get customer

  Returns a single Halo customer (client) by its ID, optionally with extra details and ticket activity.

• Action
  Get project

  Returns a single Halo project by its ID, including its details and custom fields.

• Action
  Get ticket

  Returns a single Halo ticket by its ID, optionally with extra details and its last action.

• Action
  Get user

  Returns a single Halo user (end-user contact) by ID, with optional details, ticket activity and pop-ups.

• Action
  List customers

  Returns a list of customers (clients) in Halo, optionally filtered by search text or top level.

• Action
  List tickets

  Returns tickets from Halo, optionally filtered by customer, agent, status, dates, search text and more.

• Action
  List users

  Returns the users (end-user contacts) in Halo, optionally filtered by customer, site, search text and other criteria.

• Action
  Update ticket

  Updates an existing Halo ticket's summary, details, customer, assignment, status, priority and category. Fields left blank are not changed.

• Action
  Update user

  Updates an existing Halo user's name, site, email or phone number. Fields left blank keep their current values.

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