Overview
If your Salesforce integration is not working, Mailparser will usually return an error message explaining what went wrong.
You can view these errors in your webhook logs to identify the issue.
How to Check the Error
Step 1: Open a Parsed Email
- Go to your Mailparser inbox
- Click on a processed email
Step 2: View Webhook Logs
- Navigate to the Webhooks tab
- Click on the webhook request
Here you will see the response from Salesforce, including any error messages.
Common Error and Fix
Error: Connection Error
[{"message":"INVALID_AUTH_HEADER","errorCode":"INVALID_AUTH_HEADER"}]What It Means
Your Salesforce account is not properly connected
This is required for Mailparser to send data to Salesforce.
How to Fix It
- Navigate to the Connected Account inside Settings > Connected Account and select the Re-Connect button
Field Format Errors
Examples:
[{"message":"Cannot deserialize instance of boolean from VALUE_STRING value TRUE or request may be missing a required field at [line:1, column:632]","errorCode":"JSON_PARSER_ERROR"}]What it means
The data being sent does not match the expected format in Salesforce.
Common causes
- Text sent to a numeric field
- Invalid date format (Dates should be in YYYY-MM-DD)
- Incorrect picklist value
- Boolean fields expecting true/false (need to be capitalized as TRUE/FALSE)
How to fix it
- Check your field mappings
- Ensure data formats match Salesforce requirements
- Use Mailparser filters (e.g., date formatting) to standardize values
Other Things to Check
- Your Salesforce account is properly connected
- Field mappings are correctly configured
- Required fields in Salesforce are not missing
- Your Salesforce object (Lead, Contact, etc.) is valid
Important Note
The error message shown in Mailparser comes directly from Salesforce.
This means:
- The request was sent successfully by Mailparser
- The issue occurred on the Salesforce side
Summary
If your Salesforce integration is not working:
- Check the webhook logs for the exact error
- Review the message returned by Salesforce
- Fix the issue based on the error (most commonly API access)
Most issues are caused by Salesforce configuration settings, not Mailparser itself.