SigParser analyzes your team’s emails and calendar events to identify contacts, companies, meetings, and relationships. Using configurable rules, this data is automatically exported to Salesforce, HubSpot, or Microsoft Dynamics, ensuring your CRM stays clean, complete, and up to date.
Auto Export rules allow you to control:
Which records are exported
How CRM fields are written
How existing records are updated
Because these rules run continuously in the background, teams no longer need to manually enter contacts, update company details, or track relationship activity — SigParser handles it automatically.
These rules apply across supported record types, including:
Contacts
Companies
Leads
Contact Relationships
Company Relationships
Contact Meetings
This article provides an overview of how the three configuration layers work.
For step-by-step instructions, see the Auto Export to CRM setup guide.
Record Creation Rules
Record creation rules determine which records are exported to your CRM.
Rules use IF / AND conditions, meaning a record must meet all criteria to be exported.
Common condition fields include:
Emails To / Emails From — require a minimum level of engagement
Email Status — export only contacts with valid email addresses
CRM Company — limit exports to contacts linked to existing CRM companies
Custom Fields — export records labeled as Client, Prospect, etc.
Industry — filter by company industry
Job Level — target senior roles like C-Level, Executive, Director
Domain exclusions — filter out domains like Gmail or Yahoo
Example rule set:
Emails To > 2
Emails From > 2
CRM Company is not empty
Email Status = Valid
This would export contacts with two-way engagement, a valid email address, and an existing CRM company.
❗Note: Contact records must match on email address to be eligible for export from SigParser, regardless of the rule configuration.
Field Mapping and Write Rules
Field mapping rules determine how SigParser writes values to CRM fields.
These rules are configured per field.
Rule | Behavior |
Export Always | The field is always overwritten with the current SigParser value, even if the value is blank. Use this when SigParser should be the primary source of truth for a field. |
Export Updates (Recommended default) | The field is updated only if it was last written by SigParser. If a user manually edits the value in the CRM, SigParser will not overwrite it. This is the recommended default for most fields. |
Export on Create | The field is written only when the record is first created and is not updated afterward. This is useful for initial population of fields without affecting later edits. |
Because rules are set per field, different fields in the same record type can use different behaviors.
For example:
Phone Number → Export Always
Job Title → Export Updates
Update Rules for Existing CRM Records
Update rules control whether SigParser updates records that already exist in your CRM.
These settings are configured per record type and operate independently from record creation rules.
This allows you to choose strategies such as:
Create new records but do not update existing ones
Update existing records but do not create new ones
Allow both creation and updates
Supported CRMs and Requirements
Auto Export works with:
Salesforce
HubSpot
Microsoft Dynamics
Requirements:
Professional or Enterprise SigParser subscription
A connected CRM set as Primary in SigParser’s Connectors settings
All configuration is done directly within the SigParser interface — no developer resources required.
Ready to Set It Up?
Auto Export is available on Professional and Enterprise plans.
📖 Read the full setup guide: Auto Export Records to CRM
💬Questions? Email us at support@sigparser.com or book a demo.