Connect Formstack Documents to AddToWallet

Both apps 26Formstack Documents 16AddToWallet 10

• Trigger
  New Merged Document

  Triggers when a merged/populated document is created.

• Action
  Combine Files

  Joins several files into one PDF or Word document. Give it the files in the order you want them, either as links or as base64 content, and it returns the combined file.

• Action
  Convert File to PDF

  Turns a Word, Excel, PowerPoint, image or HTML file into a PDF. Point it at the file with a link or supply the file content, and it returns the PDF.

• Action
  Copy Document

  Makes a copy of one of your Formstack Documents templates under a new name, and returns the new document with its merge key, merge URL and available merge fields.

• Action
  Create Data Route

  Creates a data route in Formstack Documents — a single endpoint that sends one set of data to several documents at once, following the rules you give it. Returns the new route with the URL to post data to.

• Action
  Create Data Route Merge

  Sends one set of data into a Formstack Documents data route, which merges it into every document the route's rules select. Optionally returns the finished documents in the response.

• Action
  Create Document

  Creates a new document template in Formstack Documents from HTML or from an uploaded PDF, Word, Excel or PowerPoint file, and returns its merge URL and the merge fields found in it.

• Action
  Delete Data Route

  Deletes a data route from Formstack Documents. The documents the route pointed at are not deleted.

• Action
  Delete Document

  Deletes a document template from Formstack Documents.

• Action
  Get Data Route

  Returns one Formstack Documents data route, with its name, its merge URL and the rules that decide which documents the data goes to.

• Action
  Get Document

  Returns one document template from Formstack Documents, with its name, type, output format, merge URL and — for HTML templates — the template's HTML.

• Action
  Get Document Fields

  Returns the merge fields found in a Formstack Documents template, so you know which names to send when merging data into it.

• Action
  List Data Routes

  Returns your Formstack Documents data routes, each with its name, key and the URL to send data to.

• Action
  List Documents

  Returns your Formstack Documents templates, each with its name, type, output format and merge URL.

• Action
  Update Data Route

  Updates a Formstack Documents data route — its name, folder, or the rules that decide which documents receive the data. Anything you leave blank stays as it is.

• Action
  Update Document

  Updates a Formstack Documents template — its name, folder, output format, filename or the template content itself. Anything you leave blank stays as it is; the template type cannot be changed.

• Action
  Add template

  Creates a reusable dynamic pass template in AddToWallet, along with a linked user group for issuing passes from it.

• Action
  Create Digital Wallet Pass

  Creates a new Apple Wallet and Google Wallet pass and returns its id and shareable link.

• Action
  Delete pass

  Archives a wallet pass by setting its state to expired, moving it to the archived section of users' wallets.

• Action
  Delete template

  Deletes a dynamic pass template and queues removal of every wallet pass issued from it.

• Action
  Get credits

  Returns the number of free and premium pass credits available on your AddToWallet account.

• Action
  Get template

  Returns the full configuration of a dynamic pass template, including its placeholders and design elements.

• Action
  List templates

  Returns all dynamic pass templates on your AddToWallet account, each with its ID and design configuration.

• Action
  Select a Pass

  Returns the wallet pass with the given ID from your AddToWallet account.

• Action
  Update pass

  Updates an existing digital wallet pass. Only the details you fill in are changed.

• Action
  Update template

  Updates an existing dynamic pass template's name, description, design or dynamic fields. Passes already created from the template are re-rendered with the new design.

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