Connect Formstack Documents to ConfigCat

Both apps 44Formstack Documents 16ConfigCat 28

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

  Create a new config within a product. POST /v1/products/{productId}/configs

• Action
  Add Flag

  Create a new feature flag or setting within a config. POST /v1/configs/{configId}/settings

• Action
  Add Segment

  Create a new segment within a product. POST /v1/products/{productId}/segments

• Action
  Add Tag

  Create a new tag within a product. POST /v1/products/{productId}/tags

• Action
  Delete Config

  Delete a config. DELETE /v1/configs/{configId}

• Action
  Delete Flag

  Delete a feature flag or setting. DELETE /v1/settings/{settingId}

• Action
  Delete Segment

  Delete a segment. DELETE /v1/segments/{segmentId}

• Action
  Delete Tag

  Delete a tag. DELETE /v1/tags/{tagId}

• Action
  Get Config

  Get a single config by id. GET /v1/configs/{configId}

• Action
  Get Environment

  Get a single environment by id. GET /v1/environments/{environmentId}

• Action
  Get Flag

  Get a single feature flag or setting by id. GET /v1/settings/{settingId}

• Action
  Get Flag value

  Get the current served value of a feature flag or setting in an environment. GET /v1/settings/{settingKeyOrId}/value

• Action
  Get Product

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

• Action
  Get Segment

  Get a single segment by id. GET /v1/segments/{segmentId}

• Action
  Get Tag

  Get a single tag by id. GET /v1/tags/{tagId}

• Action
  List Configs

  List all configs (SDK config bundles) within a product. GET /v1/products/{productId}/configs

• Action
  List Environments

  List all environments within a product. GET /v1/products/{productId}/environments

• Action
  List Flags

  List all feature flags and settings within a config. GET /v1/configs/{configId}/settings

• Action
  List Organizations

  List all organizations the caller has access to. GET /v1/organizations

• Action
  List Products

  List all products the caller has access to. GET /v1/products

• Action
  List Segments

  List all segments within a product. GET /v1/products/{productId}/segments

• Action
  List Tags

  List all tags within a product. GET /v1/products/{productId}/tags

• Action
  Update Config

  Update a config's name/description/order. PUT /v1/configs/{configId}

• Action
  Update Environment

  Update an environment's name/color/description. PUT /v1/environments/{environmentId}

• Action
  Update Flag

  Update a feature flag or setting's metadata (name, hint, tags). PATCH /v1/settings/{settingId}

• Action
  Update Flag value

  Update (turn on/off, change served value or targeting) a feature flag or setting's value in an environment. PATCH /v1/settings/{settingKeyOrId}/value

• Action
  Update Segment

  Update a segment's name/rules. PUT /v1/segments/{segmentId}

• Action
  Update Tag

  Update a tag's name/color. PUT /v1/tags/{tagId}

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