When a new form is submitted in NeetoForm, create a support ticket in Fluent Support
Each NeetoForm submission opens a ticket in Fluent Support for the person who filled in the form, so requests sent through your form go straight into your WordPress helpdesk queue.
NeetoForm
Fluent Support2 steps Setup ~5 min Used on 2.1k sites Free to import
What this workflow does
A contact or support form is easy to set up, but its replies often end up in an inbox nobody owns. Your agents work in Fluent Support, so that is where requests need to be. This workflow turns each NeetoForm response into a ticket there.
The NeetoForm trigger starts a run each time someone sends in one of your NeetoForm forms. FlowMattic passes the answers to Fluent Support, where Create a New Ticket Using Customer opens a ticket. You map the person's email and name from the form to identify the customer, and use their answers for the ticket's subject and message.
The ticket is created on the WordPress site where FlowMattic and Fluent Support run, and it enters your normal queue for assignment and replies. Your form needs an email field, because the ticket step needs to know who the customer is. Task History records each run and any error Fluent Support returns.
Help request form on a SaaS website
Users describe a problem on a NeetoForm page. Each response becomes a Fluent Support ticket your agents pick up and answer.
Warranty and return requests
Customers fill in order number and issue details. The ticket arrives in Fluent Support with that information in the message.
Event attendee questions
A pre-event questions form feeds your helpdesk, so the events team answers from one queue instead of a shared inbox.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
NeetoForm New Form SubmissionRuns when someone submits a NeetoForm form. Their answers, including any email and name fields, are passed on to the Fluent Support step.
- Fluent Support Create a New Ticket Using Customer
Opens a new ticket in Fluent Support for the customer you map. Map the email and name from the form, and use form answers for the subject and message, then submit a test response.
What you need
- FlowMatticCore
- NeetoForm AccountAccount
- Fluent Support PluginPlugin
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Make the email question required in NeetoForm so every response gives Fluent Support a customer to open the ticket for.
- If new submitters aren't accepted, add Fluent Support's Create OR Get Customer Info step before the ticket step so the customer exists first.
- Add a Filter after the trigger if one form serves several purposes and only some answers, such as a request type of Support, should become tickets.
Questions about this workflow
Does the NeetoForm submitter need to be a Fluent Support customer already?
Test with a new email address after import and check Task History. If no ticket is created, add Create OR Get Customer Info before the ticket step.
Will each NeetoForm response create its own ticket?
Yes. Every submission starts a run and opens a new ticket, even when the same person writes in twice.
Does Fluent Support have to be on the same WordPress site as FlowMattic?
Yes. Fluent Support is a WordPress plugin, and the ticket is created by the copy installed next to FlowMattic.
More Support workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted