Connect Formstack Documents to Xitoring

Both apps 32Formstack Documents 16Xitoring 16

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

  Create a new uptime/website/server check. POST /api/v2/check

• Action
  Add group

  Store a new check/server group. POST /api/v2/groups

• Action
  Add heartbeat

  Create a new heartbeat check. POST /api/v2/heartbeat/add

• Action
  Add maintenance schedule

  Create a new maintenance window. POST /api/v2/maintenance-schedules/add

• Action
  Add ticket

  Create a new support ticket. POST /api/v2/tickets

• Action
  Delete check

  Delete a check. DELETE /api/v2/checks/{id}

• Action
  Delete server

  Remove a server from monitoring. DELETE /api/v2/servers/{id}

• Action
  Get check

  Retrieve a single check by id. GET /api/v2/check/{id}

• Action
  Get incident

  Get a single incident's data. GET /api/v2/incidents/{id}

• Action
  Get server

  Retrieve a single server by id. GET /api/v2/servers/{id}

• Action
  List checks

  List all checks. GET /api/v2/check/

• Action
  List groups

  List all groups. GET /api/v2/groups

• Action
  List maintenance schedules

  List maintenance schedules. GET /api/v2/maintenance-schedules

• Action
  List servers

  List all monitored servers. GET /api/v2/servers

• Action
  Resolve incident

  Resolve an open incident. POST /api/v2/incidents/{id}/resolve

• Action
  Update check

  Update an existing check. PUT /api/v2/check/{id}

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