Connect Fluent Forms and Fluent Support

Use any Fluent Forms form as the front door to your Fluent Support helpdesk. Each submission opens a ticket for the right customer, the thank-you message can show the new ticket number, and a topic field decides the tags. Both plugins and FlowMattic run on the same WordPress site, so nothing has to leave it.

Try FlowMattic free See example workflows

8 triggers 18 actions 7 example workflows 2 ready-made templates Unlimited runs

Try a pairing

When this happens in Fluent Forms2 triggers

Do this in Fluent Support16 actions

1. TriggerNew Form Submission

2. ActionCreate a New Ticket Using Customer

When Fluent Forms fires New Form Submission, FlowMattic runs Create a New Ticket Using Customer in Fluent Support with the data from that event.

You build this in the FlowMattic workflow builder on your own site. See the setup steps

Fluent Forms and Fluent Support workflows you can build

Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.

Ready-made template

Open a support ticket from your contact form

Visitors keep using the form they know, and every message lands in Fluent Support as a ticket from that customer instead of in a shared mailbox.

New Form SubmissionCreate a New Ticket Using Customer

View the template

Show the new ticket number on the thank-you message

After the ticket is created, Set Custom Response replaces the form's usual confirmation with the ticket number, so the customer has a reference to quote in later emails.

New Form SubmissionCreate a New Ticket Using CustomerSet Custom Response

Tag each ticket by the topic chosen on the form

A dropdown for billing, technical or sales questions feeds a Router. Each path adds its own tag, so agents can filter their queue by topic from the first reply.

New Form SubmissionCreate a New Ticket Using CustomerRouterAdd Tag to Ticket (Pro)

Create an onboarding ticket for each paid setup order

Sell a setup or migration service on a Fluent Forms payment form. Every paid submission opens a ticket with the buyer's details, which becomes the job your team works through.

New Payment Submission (Pro)Create a New Ticket Using Customer

Add form answers to a ticket that is already open

A follow-up form asks for the ticket number and the extra details. The workflow fetches that ticket and posts the answers as a reply, then sends the visitor to the customer portal.

New Form SubmissionGet Specific TicketReply to TicketRedirect to Custom URL

Let staff log phone calls as tickets from an internal form

Front-desk staff fill in a short private form during a call. The ticket is opened by an agent on the caller's behalf, so phone requests sit in the same queue as email.

New Form SubmissionCreate a New Ticket Using Agent

Keep customer profiles current from an account details form

When a customer changes their phone or company on a profile form, the workflow finds them in Fluent Support and updates the record agents see next to every ticket.

New Form SubmissionCreate OR Get Customer InfoUpdate Customer

Set up: a ticket from your contact form

At the end, every submission of the form you pick opens a Fluent Support ticket for that customer.

Check both plugins
Fluent Forms and Fluent Support must be active on the same site as FlowMattic. Neither needs an entry under Connects.
Pick the form
Create a workflow with the Fluent Forms New Form Submission trigger and choose the contact form that should open tickets.
Submit a test message
Fill in the form once with a real-looking name, email, subject and message so FlowMattic has fields to map.
Create the ticket
Add Fluent Support Create a New Ticket Using Customer, map the email, name, subject and message, test the step and switch the workflow on.

Import the ready-made template Intermediate, about 5 min to set up

From Fluent Forms	To Fluent Support
Email	Customer email
First name	Customer first name
Last name	Customer last name
Subject	Ticket title
Message	Ticket content

Triggers and actions in this pair

A trigger starts a workflow. An action is something FlowMattic does in the app as a step.

Good to know

Fluent Forms actions only shape the reply to the submission that started the run, so Fluent Support events cannot write back to a form. Start these workflows from the form.
Field names depend on your form, so the mapping is an example. A form without an email field cannot create a ticket for a customer.
Tagging needs Fluent Support Pro, and payment submissions need Fluent Forms Pro with a payment method on the form.
Tickets created by these workflows still run Fluent Support's Ticket Created trigger, so other workflows that watch new tickets will pick them up too.

Fluent Forms

Integration page

Triggers (2)

New Form SubmissionTrigger the workflow when a new form submission is received
New Payment Submission (Pro)Trigger the workflow when a new payment submission is received in FluentForms Pro

Actions (2)

Set Custom ResponseSet custom response to the Fluent Form success message on form submission
Redirect to Custom URLRedirect the user to custom URL on Fluent Form submission

Fluent Support

Integration page

Triggers (6)

Ticket CreatedTriggers when a new ticket is created by either customer or agent
Agent Replies to a TicketTriggers when an agent adds a reply to the ticket
Customer Replies to a TicketTriggers when a customer adds a reply to the ticket
Agent Closes a TicketTriggers when an agent closes the ticket
Customer Closes a TicketTriggers when a customer closes the ticket
Ticket DeletedTriggers when a ticket is deleted

Actions (16)

Create a New Ticket Using AgentCreates a new ticket. Using this endpoint you will be able to create a new Customer as well as a WP user
Create a New Ticket Using CustomerCreates a new ticket
Reply to TicketReply to a ticket as a agent
Update Any ReplyUpdate any reply
Add Tag to Ticket (Pro)Add a tag to a ticket
Remove a Tag From Ticket (Pro)Remove a tag from a ticket
Get All TicketsGet all tickets
Get Specific TicketGet specific ticket by ticket id
Delete Ticket(s)Delete a ticket(s) by ticket id(s)
Delete ReplyDelete a reply by response id
Create OR Get Customer InfoCreates a new customer if not exist, or return the existing customer info
Update CustomerUpdate an existing customer
Get Customer By IDGet a specific customer by customer id
Get All CustomersGet all customers
Delete CustomerDelete a customer by customer id
Cleanup Ticket EmbedsClean up embedded attachment files in ticket content from your WordPress media directory

Why run this pair with FlowMattic

Fluent Forms and Fluent Support connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.

Your form, your helpdesk, one site

Form entries, tickets and the workflow between them all sit in your WordPress database, so customer messages never pass through an outside service.

Customers get a reference straight away

Because the workflow runs while the form responds, the confirmation can show the ticket number instead of a generic thank-you.

No limit on tickets

FlowMattic has unlimited runs on every plan, so a launch week with a flood of questions costs the same as a quiet month.

Common questions

Doesn't Fluent Support already have its own forms?

It has a ticket form in the customer portal. A Fluent Forms form lets you ask your own questions, take payments, use conditional fields and place it on any page, and FlowMattic decides how each answer is used in the ticket.

What happens if the person has never contacted support before?

Add a Create OR Get Customer Info step before the ticket. It finds the Fluent Support customer with the form's email or adds a new one, and the ticket step then uses that customer, so returning visitors keep one history.

Can I send urgent requests to a different agent?

Yes. Add a Router after the trigger with a condition on a priority or product field. Each path creates the ticket and can add a different tag, which your agents can filter on.

Can one form create tickets only for some answers?

Yes. Put a Filter before the ticket step, for example to continue only when the visitor chose Support rather than Sales. Other submissions stop there and stay as normal Fluent Forms entries.

Do I need any API keys for this pair?

No. Both plugins run on the same WordPress site as FlowMattic, so the trigger and the actions work without a connection. You only add connections for outside apps you bring into the workflow.

Did not find your answer? You can browse the help center or ask us directly.

Start automating Fluent Forms and Fluent Support

Install FlowMattic, connect both accounts and import a template. Every run stays on your own server.

Try FlowMattic free See pricing

30-day money-back guarantee Unlimited workflows and runs Self-hosted

Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Fluent Forms integration 2.1.4, Fluent Support integration 2.1.0.