Connect Formstack and Mojo Helpdesk

Both apps 46Formstack 19Mojo Helpdesk 27

• Trigger
  New Form

  Triggers when a new form is created in the account.

• Action
  Copy Form

  Create a copy of an existing form.

• Action
  Create Folder

  Create a new form folder.

• Action
  Create Form

  Create a new form.

• Action
  Create Form Field

  Add a new field to a form.

• Action
  Create Submission

  Submit data to a form. Field values are passed as field_<id> keys.

• Action
  Create Webhook

  Create a webhook on a form that POSTs to a URL when a submission is received.

• Action
  Delete folder

  Delete a folder.

• Action
  Delete Form

  Delete a form by ID.

• Action
  Delete Submission

  Delete a submission by ID.

• Action
  Delete Webhook

  Delete a webhook by ID.

• Action
  Get folder

  Get a folder by id.

• Action
  Get Form

  Retrieve details for a single form by ID.

• Action
  Get form field

  Get one field on a form.

• Action
  List Form Confirmations

  List confirmation emails configured on a form.

• Action
  List Form Fields

  List all fields on a form.

• Action
  List form notifications

  List notification emails for a form.

• Action
  List Webhooks

  List webhooks configured on a form.

• Action
  Update folder

  Update a folder.

• Trigger
  New Ticket

  Triggers when a new ticket is created in Mojo Helpdesk.

• Trigger
  New Ticket With Due On

  Triggers when a new Mojo Helpdesk ticket that has a due date is created.

• Trigger
  New Ticket With Scheduled On

  Triggers when a new Mojo Helpdesk ticket that has a scheduled date is created.

• Trigger
  New User

  Triggers when a new user is created in Mojo Helpdesk.

• Action
  Add asset

  Creates a new asset in Mojo Helpdesk Asset Management and returns the created asset.

• Action
  Add Comment to Ticket

  Adds a public comment to a Mojo Helpdesk ticket.

• Action
  Add Staff Note to Ticket

  Adds an internal staff-only note to a Mojo Helpdesk ticket.

• Action
  Add Tag to Ticket

  Adds a tag to a Mojo Helpdesk ticket, creating the tag if it does not exist.

• Action
  Add task to ticket

  Creates a task on a ticket, with optional notes, due date, assignee and completion status.

• Action
  Create Ticket

  Creates a new ticket in Mojo Helpdesk and returns it.

• Action
  Create User

  Creates a new user in Mojo Helpdesk.

• Action
  Delete ticket

  Permanently deletes a ticket, including its comments and attachments.

• Action
  Delete user

  Permanently deletes a user from Mojo Helpdesk. This cannot be undone.

• Action
  Find assets by criteria

  Returns the assets that match a search query, such as a name, tag, serial number, location or assigned user.

• Action
  Find User by Email

  Finds a Mojo Helpdesk user by email address.

• Action
  Get asset

  Returns the details of a single asset, including its status, location, assigned users and attached files.

• Action
  Get Ticket

  Returns one Mojo Helpdesk ticket by its ID, including title, description, status, priority and assignee.

• Action
  Get User

  Returns one Mojo Helpdesk user by ID.

• Action
  List comments

  Returns the comments on a Mojo Helpdesk ticket, including staff notes.

• Action
  List ticket queues

  Returns the ticket queues in your Mojo Helpdesk account, with each queue's id, name and email settings.

• Action
  List tickets

  Returns the tickets in your Mojo Helpdesk, sorted by the field and order you choose.

• Action
  List users

  Returns the users (end users and agents) in your Mojo Helpdesk account.

• Action
  Remove tag from ticket

  Removes a tag from a ticket, identified by the tag's ID or label, and returns the ticket's remaining tags.

• Action
  Search Tickets

  Finds Mojo Helpdesk tickets matching a search query (same syntax as the web app's advanced search).

• Action
  Update asset

  Updates an existing asset in Mojo Helpdesk, changing only the fields you supply.

• Action
  Update Ticket

  Updates an existing Mojo Helpdesk ticket; only the fields you supply change.

• Action
  Update User

  Updates a Mojo Helpdesk user's details; only the fields you supply change (email cannot be changed here).

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