Connect Doclift PDF to Propelauth

Both apps 24Doclift PDF 12Propelauth 12

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

• Action
  Add user

  Creates a new user in your PropelAuth environment and returns the new user's ID.

• Action
  Block user

  Blocks (disables) a PropelAuth user, preventing them from logging in until they are unblocked.

• Action
  Create access token

  Generates an access token for a PropelAuth user with a chosen duration, useful for testing your backend without a frontend.

• Action
  Create magic link

  Creates a magic login link for a user and returns its URL. The link is not emailed; you deliver it yourself.

• Action
  Delete user

  Permanently deletes a PropelAuth user and all of their data.

• Action
  Find user by email

  Finds a PropelAuth user by their email address and returns their profile, custom properties and, optionally, their organizations.

• Action
  Find user by username

  Finds a user by their username (when usernames are enabled) and returns their full profile.

• Action
  Get user

  Returns a user's details, including their profile, status, custom properties and optionally their organizations.

• Action
  List users

  Returns the users in your PropelAuth project, optionally filtered by partial email or username and sorted.

• Action
  Unblock user

  Unblocks (re-enables) a blocked PropelAuth user so they can log in again.

• Action
  Update user

  Updates a user's username, name, profile picture, custom properties, legacy ID or password-reset requirement.

• Action
  Update user email

  Changes a user's email address, either immediately or after the user confirms the new address by email.

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