Connect Doclift PDF and Givecloud

Both apps 30Doclift PDF 12Givecloud 18

• 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
  Contribution Paid

  Triggers when a new contribution (donation or purchase) is placed in Givecloud.

• Trigger
  New Supporter

  Triggers when a new supporter (donor) is created in Givecloud.

• Trigger
  Supporter Updated

  Triggers when a Givecloud supporter (donor) is created or updated.

• Action
  Create Sponsee

  Creates a new Givecloud sponsee (a child or project available for sponsorship).

• Action
  Delete Sponsee

  Deletes a Givecloud sponsee.

• Action
  Get Contribution

  Returns one Givecloud contribution (donation or purchase) by ID.

• Action
  Get Post

  Returns one post from a Givecloud feed.

• Action
  Get Product

  Returns one Givecloud product by ID, optionally with its categories and variants.

• Action
  Get Recurring Profile

  Returns one Givecloud recurring giving profile by ID.

• Action
  Get Sponsee

  Returns one Givecloud sponsee by ID.

• Action
  Get Supporter

  Returns one Givecloud supporter (donor) by ID, with addresses and memberships.

• Action
  List Contributions

  Returns Givecloud contributions (donations and purchases), optionally filtered by date or one-time vs. recurring.

• Action
  List Posts

  Returns the posts in a Givecloud feed (such as news or blog entries).

• Action
  List Products

  Returns Givecloud products (donation forms and store items), optionally filtered by code or name.

• Action
  List Recurring Profiles

  Returns Givecloud recurring giving profiles (monthly donations and other scheduled gifts).

• Action
  List Sponsees

  Returns Givecloud sponsees (sponsored children or projects), optionally filtered by name or reference number.

• Action
  List Supporters

  Returns Givecloud supporters (donors), optionally filtered by name, email or recurring-gift status.

• Action
  Update Sponsee

  Updates an existing Givecloud sponsee; only the fields you supply change.

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