Membership sites, course sites and SaaS businesses on WordPress often run support in Desku.io. FlowMattic keeps the two lined up from inside WordPress: customers and users are created on both sides, site events such as a role change or a support question in the comments open tickets, and solved tickets can become draft help articles.
40 triggers 73 actions 7 example workflows 6 ready-made templates Unlimited runs
When this happens in WordPress32 triggers
Do this in Desku.io2 actions
1. TriggerNew User2. ActionCreate TicketWhen WordPress fires New User, FlowMattic runs Create Ticket in Desku.io with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
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 templateCustomers added in Desku, for example from live chat, get a matching site account, so they can log in to the member area or knowledge base on your site.
Add New CustomerNew User
View the template Every new WordPress registration is created as a customer in Desku with name and email, so agents see who the person is when their first ticket arrives.
New UserCreate Customer
Agents often correct names or emails during a ticket. Update Customer finds the user by email and updates their WordPress profile to match.
Update CustomerGet User by EmailUpdate User
A role change to your paid membership role opens a Desku ticket assigned to onboarding, so a person welcomes each new premium member and books their setup call.
User Role ChangedFilterCreate Ticket
An AI Agent reads each new comment and decides whether it is a support request. Those that are become Desku tickets, so they are answered in the helpdesk instead of under a post.
New CommentAI AgentFilterCreate Ticket
When a ticket changes to solved, an AI Agent writes a short how-to from the question and answer, and FlowMattic saves it as a WordPress post for an editor to review.
Change Ticket StatusFilterAI AgentNew Post
Ready-made templateWhen another system, such as a checkout or a booking tool, posts a new customer to FlowMattic, a WordPress user is created and a Desku ticket opens to start their onboarding.
WebhookNew UserCreate Ticket
View the templateWhen you finish, each new customer created in Desku.io gets a WordPress user account with the same name and email.
Add your Desku.io account under Connects. WordPress is the site FlowMattic runs on, so it needs no connection.
Create a workflow with the Desku.io Add New Customer trigger, follow the steps it shows and create a test customer in Desku.
Add Get User by Email and a Router, so a customer who already has a site account is not created twice.
Add WordPress New User, map the email, name and a username, choose the role, test it and switch the workflow on.
1. Trigger in Desku.io
Add New Customer
2. Action in WordPress
New User
Fields mapped from the earlier steps (a typical setup)
| From WordPress | To WordPress |
|---|---|
| Customer email | User email |
| Customer name | First and last name |
| Customer email | Username |
| Fixed value | Role, such as subscriber |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
WordPress and Desku.io connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Customers, users and tickets line up, so agents and site admins are looking at the same people.
Role changes, comments and webhooks from your WordPress site become tickets in Desku, without anyone copying details across.
FlowMattic works inside WordPress with unlimited runs, so user data does not pass through another automation service.
Yes. Start a FlowMattic workflow with the Desku.io Add New Customer trigger and add the WordPress New User action. Map the name and email and choose the role new accounts should get.
Yes. Choose the role in New User, or change it later with Change User Role or Add Role to User, for example when a Desku.io customer moves to a paid plan.
Yes. Use your form plugin's trigger, or a Webhook, and add Create Ticket with the subject and message from the form.
Not through these actions, which create customers and tickets but do not read them back. Change Ticket Status and other Desku triggers can write details to user meta with Update User Meta if you want a record on the site.
It does not have to be. Add a Human in the Loop step before New Post so an editor approves the AI Agent's text, or save it with a draft status and publish it by hand.
Did not find your answer? You can browse the help center or ask us directly.
WordPress and Slack17 shared templates
WordPress and Contact Form 715 shared templates
WordPress and LearnDash13 shared templates
WordPress and Brevo (Sendinblue)13 shared templates
WordPress and OpenAI (ChatGPT)11 shared templates
WordPress and Google Sheets10 shared templates
WordPress and Tutor LMS8 shared templates
WordPress and FluentCRM7 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 23 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. WordPress integration 7.3.0, Desku.io integration 1.0.
