Connect Feathery and Formstack Documents

Both apps 29Feathery 13Formstack Documents 16

• Trigger
  Data Received

  Triggers when an end user submits or updates data on a Feathery form.

• Trigger
  Form Completion

  Triggers when an end user completes a Feathery form.

• Action
  Create Hidden Field

  Creates a hidden field in your Feathery account.

• Action
  Create or Fetch User

  Creates a Feathery end user with the given ID, or returns the existing user, including its SDK key.

• Action
  Create or Update Submission

  Sets field values for a Feathery user and initializes submissions on the given forms.

• Action
  Delete User

  Deletes a Feathery end user and their submissions.

• Action
  Get User Field Data

  Returns every field value a Feathery user submitted across forms.

• Action
  Get User Form Session

  Returns a Feathery user's form session: every form they are working on and their progress.

• Action
  List Document Templates

  Returns document templates uploaded by your Feathery team, optionally filtered by name or tags.

• Action
  List Forms

  Returns your Feathery forms, optionally filtered by tags or active status.

• Action
  List Form Submissions

  Returns submissions for a Feathery form, optionally filtered by user, completion and update time.

• Action
  List Hidden Fields

  Returns all hidden fields in your Feathery account.

• Action
  List Users

  Returns your Feathery end users, optionally filtered by creation time or a field value.

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

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