Many leads and requests still arrive as email: portal notifications, supplier orders, support messages. FlowMattic's Email Parser gives you an address to forward them to, reads each one, and creates the matching ticket, contact or deal in HubSpot CRM. For sales and support teams who want those emails on a record, not in an inbox.
2 triggers 25 actions 6 example workflows 1 ready-made template Unlimited runs
When this happens in Email Parser2 triggers
Do this in HubSpot CRM25 actions
1. TriggerEmail Received2. ActionCreate TicketWhen Email Parser fires Email Received, FlowMattic runs Create Ticket in HubSpot CRM 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 templateA Filter keeps emails whose subject or sender matches your support address, and Create Ticket opens a ticket with the subject and body, so no request is left in a shared inbox.
Email ReceivedFilterCreate Ticket
View the template Listing sites and marketplaces email you each enquiry. Text Formatter pulls the name and email out of the body and Create Contact adds the lead to HubSpot.
Email ReceivedText FormatterCreate Contact
An AI Agent reads a free-form purchase request and returns the company, product and amount, which Create Deal uses to put the order in the pipeline.
Email Received (v2)AI AgentCreate Deal
Get Contact looks up the sender's email. A Router updates the existing contact with the latest message date, or creates a contact for someone new.
Email ReceivedGet ContactRouterUpdate Contact
Registration confirmations forwarded to the parser create the contact and Add Contact To List puts them on the webinar list for follow-up emails.
Email ReceivedCreate ContactAdd Contact To List
Partners email you introductions. Create Company adds the referred business and Create Contact adds the person, so the referral is credited in HubSpot.
Email Received (v2)Create CompanyCreate Contact
At the end, every support email you forward to the parser address opens a ticket in HubSpot CRM.
Under Connects in FlowMattic, add a HubSpot CRM connection with an account that can create tickets and contacts.
Create a workflow with Email Parser and Email Received, and copy the email address FlowMattic gives you for it.
Set your support mailbox to forward to that address, or forward one email by hand, so FlowMattic captures the sender, subject and body.
Add a Filter that continues only when the sender or subject matches support mail, so newsletters and receipts are skipped.
Add HubSpot CRM Create Ticket, map the subject and body, pick the pipeline and stage, test the step and switch the workflow on.
1. Trigger in Email Parser
Email Received
3. Action in HubSpot CRM
Create Ticket
Fields mapped from the earlier steps (a typical setup)
| From Email Parser | To HubSpot CRM |
|---|---|
| Subject | Ticket name |
| Body (plain text) | Ticket description |
| From email | Associated contact email |
| Received date | Create date |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Email Parser and HubSpot CRM connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Tickets, contacts and deals are created from the email itself, so the team works from HubSpot instead of a forwarded thread.
The parser and the workflow run on your own WordPress site, so the email content passes only between your site and HubSpot.
FlowMattic runs are unlimited, so a support address that gets hundreds of emails a day needs no bigger plan.
Use FlowMattic's Email Parser Email Received trigger, forward your support mail to the address it gives you, then add HubSpot CRM Create Ticket with the subject and body mapped. A Filter before it can skip mail you do not want as tickets.
Yes. Text Formatter can extract text between known labels for emails in a fixed format. For emails written freely, an AI Agent step can read the body and return the fields you ask for.
Avoid that with Get Contact on the sender's email, then a Router: update the contact when it exists, create one when it does not.
The workflow can read what the parser captures from each email. Test with an email that has an attachment to see which details are available to map into the ticket or note.
Contacts, companies, deals, tickets, products and line items all have create actions, and contacts can be added to or removed from lists.
Did not find your answer? You can browse the help center or ask us directly.
Email Parser and Google Sheets3 shared templates
Email Parser and WooCommerce3 shared templates
Email Parser and Slack2 shared templates
Email Parser and Airtable2 shared templates
Email Parser and Google Drive2 shared templates
Email Parser and WordPress2 shared templates
Email Parser and Gmail1 shared template
Email Parser and Monday.com1 shared templateHubSpot CRM and Google Sheets7 shared templates
HubSpot CRM and Facebook Lead Ads5 shared templates
HubSpot CRM and Fluent Forms5 shared templates
HubSpot CRM and Gravity Forms4 shared templates
HubSpot CRM and Typeform2 shared templates
HubSpot CRM and WooCommerce2 shared templates
HubSpot CRM and Airtable2 shared templates
HubSpot CRM and Jotform2 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 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Email Parser integration 1.0, HubSpot CRM integration 1.3.0.