Connect Formstack Documents to Intercom

Both apps 54Formstack Documents 16Intercom 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 company

  Fires when a new company is created. Poll GET /companies ordered by created_at.

• Trigger
  New conversation

  Polls for conversations, most recently updated first. Fires for each new conversation.

• Trigger
  New lead

  Instant trigger: fires when a new lead is created in Intercom (webhook). Stub ported from dev.apiant — not yet implemented.

• Trigger
  New note on conversation

  Instant trigger: fires when a note is added to an Intercom conversation (webhook). Stub ported from dev.apiant — not yet implemented.

• Trigger
  New or updated contact

  Polls for contacts, most recently updated first. Fires for each new or updated contact.

• Trigger
  New tag on a conversation

  Instant trigger: fires when a tag is added to an Intercom conversation (webhook). Stub ported from dev.apiant — not yet implemented.

• Trigger
  New tag on a user

  Instant trigger: fires when a tag is added to an Intercom user (webhook). Stub ported from dev.apiant — not yet implemented.

• Trigger
  New ticket

  Fires when a new ticket is created. Poll GET /tickets/search or /tickets ordered by created_at.

• Action
  Add company

  Create (or upsert) a company in Intercom. POST /companies.

• Action
  Add note to contact

  Adds a note to the specified contact as the specified admin.

• Action
  Add note to conversation

  Adds an internal note to the specified conversation as an admin.

• Action
  Add tag to contact

  Attaches a tag to the specified contact.

• Action
  Add ticket

  Create a support ticket. POST /tickets.

• Action
  Assign conversation

  Assigns the conversation to an admin or team.

• Action
  Close conversation

  Closes the specified conversation.

• Action
  Create contact

  Creates a new contact (role user or lead) in Intercom.

• Action
  Create message

  Creates an admin-initiated email or in-app message to a contact.

• Action
  Delete company

  Delete a company by ID. DELETE /companies/{company_id}.

• Action
  Delete contact

  Deletes a contact by ID.

• Action
  Find admin by email

  Fetches an admin's details. Lists all admins; match by email.

• Action
  Find contact by email

  Searches contacts by email and returns matches.

• Action
  Find tickets

  Search tickets by criteria. POST /tickets/search.

• Action
  Get company

  Retrieve a company by ID. GET /companies/{company_id}.

• Action
  Get contact

  Fetches a contact's details by ID.

• Action
  Get conversation

  Fetches a conversation's details by ID.

• Action
  Get ticket

  Retrieve a ticket by ID. GET /tickets/{ticket_id}.

• Action
  List companies

  List all companies. GET /companies.

• Action
  List segments

  List all segments. GET /segments.

• Action
  List tags

  Lists all tags for the workspace.

• Action
  Open conversation

  Opens (marks open) the specified conversation.

• Action
  Remove tag from contact

  Detaches a tag from the specified contact.

• Action
  Send conversation reply

  Sends a reply to the specified conversation as an admin.

• Action
  Snooze conversation

  Snoozes the specified conversation until the given unix timestamp.

• Action
  Start conversation

  Starts a new conversation with the specified contact.

• Action
  Track event

  Submit a data event for a contact. POST /events.

• Action
  Update company

  Update an existing company. PUT /companies/{company_id}.

• Action
  Update contact

  Updates an existing contact specified by ID.

• Action
  Update ticket

  Update an existing ticket. PUT /tickets/{ticket_id}.

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