Connect Amplifier and Doclift PDF

Both apps 28Amplifier 16Doclift PDF 12

• Trigger
  New Item

  Triggers when a new inventory item is created in Amplifier.

• Trigger
  New Order Received

  Triggers when a new order is received in Amplifier.

• Action
  Create Item

  Creates an inventory item (SKU) in Amplifier.

• Action
  Create Order

  Creates a fulfillment order in Amplifier with a ship-to address and line items.

• Action
  Create Order Source

  Creates an order source, the channel label you attach to orders.

• Action
  Create Receipt

  Creates an inbound receipt telling Amplifier a supply delivery of boxes is on its way.

• Action
  Delete Order Source

  Deletes an order source.

• Action
  Find Items

  Searches inventory items by SKU, name or free text and returns the matches.

• Action
  Get Campaign

  Returns one campaign by its ID, with its dates, reward limits and notification settings.

• Action
  Get Current Inventory

  Returns current inventory levels for every item in your Amplifier account.

• Action
  Get Item

  Returns one inventory item by its Amplifier ID, including SKU, name, pricing and dimensions.

• Action
  Get Order

  Returns one order by its Amplifier ID, including status, shipping details and line items.

• Action
  Get Order Source

  Returns one order source by its ID, with its name and code.

• Action
  Get Shipments By Ship Date

  Returns the shipments that shipped on a given date.

• Action
  List Campaigns

  Returns the campaigns in the Amplifier account.

• Action
  Revoke Campaign Offer

  Revokes a campaign offer so it can no longer be redeemed.

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