Email Parser Integrations for Webhooks, Sheets, CRM, and Storage

MailSlurp email parser integrations move structured results from an inbox into a webhook endpoint, spreadsheet, CRM, database, queue, or file store. The right destination depends on what should happen after extraction: update application state, give a team a shared work list, preserve an attachment, or notify someone who can act.

Choose the destination by the job it must do

Destination	Best for	Delivery detail to plan
Webhook, API, or queue	Application workflows and event-driven processing	Authenticate requests, acknowledge quickly, and process idempotently
Database	Canonical records, joins, and transactional updates	Validate before the write and preserve source identifiers
Google Sheets or Excel	Shared operational views, review queues, and light reporting	Upsert by a stable key instead of appending every delivery
CRM or ticketing system	Lead, customer, and support workflows	Separate create and update rules to avoid duplicate contacts or tickets
Google Drive or Dropbox	Original PDFs, receipts, and evidence files	Store the attachment ID beside the destination file URL
Slack or Trello	Human alerts and follow-up tasks	Link back to the source or review record instead of pasting sensitive content

If a spreadsheet is only a view onto a business-critical process, keep the canonical state in your database or queue and sync the fields people need to the sheet.

The integration flow

Receive a completed result

Attach a webhook to a MailSlurp AI transformer and listen for NEW_AI_TRANSFORM_RESULT. The webhook payload includes:

• messageId, an idempotent event ID for detecting repeat delivery;
• aiTransformResultId, which you can use to fetch the full transform result;
• aiTransformId, identifying the transformer that produced it;
• entityId and entityType when the result came from a mapped inbox or phone entity;
• result, a JSON string when the result is included in the event.

Return a successful response promptly, then perform slower destination work asynchronously when possible.

Validate and normalize

Parse the JSON, validate it against the expected schema, and apply business checks before sending it elsewhere. Normalize dates, currency codes, phone numbers, and controlled status values at this boundary. Keep absent values absent rather than turning them into plausible-looking guesses.

Write once, even when delivery repeats

Webhook delivery can be retried. Store messageId as the event-level idempotency key and retain aiTransformResultId as the result trace. For the destination record, use a business key such as an invoice number plus supplier, an order ID, or an existing contact ID. This lets a repeated event update the intended record instead of creating another one.

Record the outcome

Keep the destination record ID, delivery status, last attempt time, and error details with the transform result ID. A useful audit trail answers three questions quickly: which email produced this data, where was it written, and can the write be tried again safely?

Example handoff

An invoice workflow might follow this sequence:

1. A supplier email arrives in a MailSlurp inbox and matches the invoice transformer.
2. MailSlurp extracts a typed invoice result and sends a NEW_AI_TRANSFORM_RESULT webhook.
3. Your handler checks messageId, fetches the full result using aiTransformResultId, and validates the required fields.
4. The PDF is stored in Drive, the canonical invoice record is upserted in your database, and a review row is updated in Google Sheets.
5. Each destination ID is stored against the transform result so a failed step can be retried without repeating successful work.

This pattern also works for order confirmations, support intake, application forms, and shipment updates. Only the schema, business key, and destinations change.

Destination guides

For structured rows and shared operational views, use the Google Sheets integration or Microsoft Excel integration. For original files and evidence, use Google Drive or Dropbox.

For team and customer workflows, see the HubSpot integration, Salesforce integration, Slack integration, or Trello integration.

When your application should own the complete handoff, start with the email parser API and the AI structured extraction product guide.