--- title: "SigParser Integration" description: "SigParser is a stateless email parsing API that extracts contact details from email signatures and strips signatures and reply chains from message bodies. Agents turn a raw or MIME email into clean contact records and a clean message body before pushing it to a CRM." url: https://flowrunner.ai/integrations/sigparser date_modified: 2026-09-04T19:45:02-07:00 --- # SigParser [Sales Intelligence](https://flowrunner.ai/integrations/category/crm-sales) SigParser is a stateless email parsing API that extracts contact details from email signatures and strips signatures and reply chains from message bodies. Agents turn a raw or MIME email into clean contact records and a clean message body before pushing it to a CRM. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 3 actions · API key · available [SigParser website](https://sigparser.com/) · [Platform Documentation](https://www.sigparser.com/developers) · Capability data verified 2026-08-27 1. A reply lands in the shared sales mailbox and the flow picks it up 2. Parse Email returns every signature in the thread plus the body with quoted replies stripped 3. The agent reads the spam and automated sender flags before treating any signature as a person 4. Each parsed contact is matched against the CRM to separate refreshes from genuinely new people 5. Known contacts get their title, direct line, and mobile updated on the existing record 6. The rep gets a summary of what changed and what is waiting 7. The rep decides which names found deeper in the thread belong in the CRM at all ## What This Integration Enables SigParser is a parser, not a database. It stores nothing, remembers nothing between calls, and hands back only what it found in the message you gave it. That is the whole reason it fits in a flow: the connector sits between a mailbox and whatever system owns your contact data, and it never becomes a second place where contact records live. Agents pass in a message, get back structured contacts and a cleaned body, and write the result into the system of record that already exists. What it finds is more than the sender. SigParser reads every signature in a message, including the ones buried in a reply chain, and splits each one into name, title, company, a postal address broken into parts, phone numbers separated by kind, and social handles. That is genuinely useful and it is also the reason this page has a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate: an agent that writes every signature it finds straight into the CRM will create contact records for people who never emailed your company. Parsing is a machine job. Deciding who becomes a contact is not. ### Without FlowRunner **Signatures retyped by hand**: Direct lines and titles are copied out of emails one at a time, or not at all **Stale contact records**: A title changes in someone's signature months before it changes in the CRM **Quoted replies in the CRM**: Logged email activity carries the whole thread, so the useful part is buried ### With FlowRunner **Contact detail read on arrival**: Every signature in the message is parsed into typed fields the moment the mail lands **Records refreshed from live mail**: A new mobile number or job title in a signature updates the record it belongs to **Clean bodies stored**: The logged message is the message, with the signature and the quoted chain removed ## Use Case Scenarios ### Inbound replies keep the CRM current A reply arrives in the shared mailbox through [Gmail](https://flowrunner.ai/integrations/gmail-service) or [Outlook](https://flowrunner.ai/integrations/outlook). The agent calls Parse Email with both the HTML and plain text bodies, because LinkedIn and X URLs are usually only recoverable from the markup. It reads the spam and automated sender flags first, so a newsletter's no-reply footer never reaches the CRM. For the sender's own signature it matches on email address and refreshes the title, office line, and mobile on the existing record in [HubSpot](https://flowrunner.ai/integrations/hubspot) or [Attio](https://flowrunner.ai/integrations/attio). The cleaned body, not the raw thread, is what gets logged as the activity. ### Archived mail turned into structured history A migration flow reads EML files out of storage and passes each one to Parse MIME Email, which splits the chain into individual messages, parses the headers, and returns the spam indicators. Each message in the chain carries a flag saying whether it parsed correctly, and parsing quality drops the deeper into a chain you go, so the agent routes anything flagged as a poor parse into a review queue instead of a write. What survives the pass lands in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the RevOps owner to approve as a batch. ### A support thread that quietly names the real decision maker A thread from [Zendesk](https://flowrunner.ai/integrations/zendesk) gets forwarded into the flow. Parse Email finds three signatures: the requester, a colleague copied halfway through, and a signature from an outside vendor further down. The agent enriches only the requester automatically, posts the other two to the account owner in [Slack](https://flowrunner.ai/integrations/slack) with the line of the thread each came from, and waits. The owner adds one to the account and ignores the other. The agent never guessed. ## Human-in-Loop Highlight The dangerous capability here is the one that sells the product: SigParser returns every signature it can find, including ones from people deep in a forwarded chain who never wrote to your company and have no idea it holds their details. An agent that treats that list as a contact import is making a data protection decision at machine speed on the strength of a parse. So the flow splits the result. Signatures whose email address matches the message's own sender are refreshed automatically, because that person emailed you. Everything else stops and posts to the account owner: "This thread contained two other signatures. Jordan Ellis, Operations Director at Kestrel Freight, appeared in a message forwarded from outside the account. Add as a contact, or drop?" The owner answers in the channel. The parse was the agent's work. The decision about whose details you keep was never the agent's to make. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 3 actions ### Email Parsing 2 - **Parse Email** Extracts contact details from every signature in an email, including signatures deeper in the reply chain, and returns the body with signatures and quoted replies stripped. Each contact carries name, title, company, phone numbers split by kind, a structured postal address, and LinkedIn and X handles. The response also flags whether the message or the sender looks automated rather than human, which is the check to make before writing a contact into a CRM. Supply the HTML body where you have it, because social URLs are usually only discoverable from the markup. - **Parse MIME Email** Parses a complete MIME encoded email, which is what the contents of an EML file are, and returns the cleaned bodies, the whole reply chain split into individual messages, the parsed headers, and the spam indicators. Use this when the raw message is what you have. Each message in the chain carries a flag saying whether it parsed correctly, because header formats vary between clients and parsing quality drops the deeper into a chain you go. ### Account 1 - **Test Connection** Verifies that the configured API key reaches SigParser and returns the key's prefix so you can confirm which key answered. It takes no input and parses nothing, which makes it the right first step when a flow is failing and you need to separate a credential problem from a parsing one. ## Frequently Asked Questions ### What can FlowRunner do with SigParser? FlowRunner agents can run Parse Email, Parse MIME Email, and Test Connection in SigParser. ### Does connecting SigParser to FlowRunner require OAuth? No. SigParser connects to FlowRunner with an API key, no OAuth flow required. ### Can SigParser trigger a FlowRunner workflow automatically? SigParser doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at SigParser?** This integration exposes SigParser to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/sigparser. Site index: https://flowrunner.ai/llms.txt