Connect Formstack Documents to Frihet

Both apps 54Formstack Documents 16Frihet 38

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

• Trigger
  New Expense

  Fires when a new expense is created. Backed by vendor webhook registration (POST /v1/webhooks, event=expense.created).

• Action
  Add Client

  Create a client. POST /v1/clients

• Action
  Add Deposit

  Create a deposit. POST /v1/deposits

• Action
  Add Expense

  Create an expense. POST /v1/expenses

• Action
  Add Invoice

  Create an invoice. POST /v1/invoices

• Action
  Add Product

  Create a product. POST /v1/products

• Action
  Add Quote

  Create a quote. POST /v1/quotes

• Action
  Add Vendor

  Create a vendor. POST /v1/vendors

• Action
  Apply deposit to invoice

  Apply a deposit balance to an invoice. POST /v1/deposits/{depositId}/apply

• Action
  Delete Client

  Delete a client. DELETE /v1/clients/{clientId}

• Action
  Delete Expense

  Delete an expense. DELETE /v1/expenses/{expenseId}

• Action
  Delete Invoice

  Delete an invoice. DELETE /v1/invoices/{invoiceId}

• Action
  Delete Product

  Delete a product. DELETE /v1/products/{productId}

• Action
  Delete Quote

  Delete a quote. DELETE /v1/quotes/{quoteId}

• Action
  Delete Vendor

  Delete a vendor. DELETE /v1/vendors/{vendorId}

• Action
  Get Client

  Retrieve a client by id. GET /v1/clients/{clientId}

• Action
  Get Deposit

  Retrieve a deposit by id. GET /v1/deposits/{depositId}

• Action
  Get Expense

  Retrieve an expense by id. GET /v1/expenses/{expenseId}

• Action
  Get Invoice

  Retrieve an invoice by id. GET /v1/invoices/{invoiceId}

• Action
  Get Product

  Retrieve a product by id. GET /v1/products/{productId}

• Action
  Get Quote

  Retrieve a quote by id. GET /v1/quotes/{quoteId}

• Action
  Get Vendor

  Retrieve a vendor by id. GET /v1/vendors/{vendorId}

• Action
  List Clients

  List clients. GET /v1/clients

• Action
  List Deposits

  List deposits. GET /v1/deposits

• Action
  List Expenses

  List expenses. GET /v1/expenses

• Action
  List Invoices

  List invoices. GET /v1/invoices

• Action
  List Products

  List products. GET /v1/products

• Action
  List Quotes

  List quotes. GET /v1/quotes

• Action
  List Vendors

  List vendors. GET /v1/vendors

• Action
  Mark invoice as paid

  Mark an invoice as paid. POST /v1/invoices/{invoiceId}/paid

• Action
  Send Invoice

  Send invoice by email to the client. POST /v1/invoices/{invoiceId}/send

• Action
  Send Quote

  Send quote by email to the client. POST /v1/quotes/{quoteId}/send

• Action
  Update Client

  Partial update a client. PATCH /v1/clients/{clientId}

• Action
  Update Expense

  Partial update an expense. PATCH /v1/expenses/{expenseId}

• Action
  Update Invoice

  Partial update an invoice. PATCH /v1/invoices/{invoiceId}

• Action
  Update Product

  Partial update a product. PATCH /v1/products/{productId}

• Action
  Update Quote

  Partial update a quote. PATCH /v1/quotes/{quoteId}

• Action
  Update Vendor

  Partial update a vendor. PATCH /v1/vendors/{vendorId}

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