Use your GHL API credentials to authorize requests to the Snapshots API. Ensure your API key has the saas/location.read scope and that your app is granted access to the relevant endpoints.
Auth for the Mailparser integration typically relies on tokens generated in Mailparser alongside your GHL access token to authorize calls. Store credentials securely and rotate them regularly.
GET /locations — Retrieves location data for your Snapshots API account. Additional endpoints exist in the API docs for advanced usage.
Trigger: A new parsed email is ready in Mailparser and should be recorded in Snapshots. Map parsed fields to the Snapshots location fields to create or update records in real time.
Actions: create or update a location record in Snapshots; map fields such as location_id, name, address, and timestamp
GET /locations
Key fields: location_id, name, address, city, country, timestamp
Trigger: Daily batch of parsed emails collected by Mailparser is ready for import into Snapshots
Actions: upsert multiple location records in a single request; handle deduplication by location_id
POST /locations/batch
Key fields: batch_id, timestamp, locations (array of location objects)
Trigger: On-demand parsing results trigger a lookup for specific location data in Snapshots
Actions: fetch location data using GET /locations and merge with parsed fields
GET /locations/{id}
Key fields: id, location_id, external_id
Automate data transfer between Mailparser and Snapshots API without writing code
Build and test workflows visually with a no-code connector
Scale your data processes as Mailparser volumes grow
Definitions for common terms used in GHL integrations: endpoints, triggers, actions, fields, and authentication.
A RESTful API exposed by GHL that lets apps read and write data with proper authentication and scoped permissions.
A specific URL in the API that performs a resource operation, such as GET /locations to fetch location data.
An event that starts a workflow, such as a new parsed email or a new contact being created.
The method by which apps prove identity to access the API, typically via API keys or OAuth tokens.
Automatically enrich new Mailparser results by creating or updating location records in Snapshots API.
Use templates to map parsed data to Snapshots fields for a consistent setup.
Produce detailed logs of every data transfer for compliance and troubleshooting.
Obtain your GHL API key and create a Mailparser integration token
Select GET /locations and map Mailparser fields to Snapshots fields
Run a test parse, verify data in Snapshots, and enable automatic runs
No coding is required to connect Mailparser with Snapshots API. The no-code bridge lets you map fields and set triggers without writing scripts. If you need more complex logic, you can use conditional steps or intermediate transforms provided by the GHL connector.
Yes, basic setups can be done with tokens and UI-only configuration. For advanced logic and data transformations, you might add simple workflows with built-in functions. If you need more complex data shaping, use tests and validation steps available in the connector.
Basic endpoints include GET /locations to read location data. Use the endpoint list to see compatibility with your Mailparser data. For more complex queries, refer to the full API docs and examples.
Authenticate with a GHL API key and a Mailparser integration token. Ensure tokens are kept secure. If you rotate keys, update the configuration in the app connector.
Bulk transfers are supported via batch endpoints when available. This helps move multiple parsed items into Snapshots in one call. For real-time bulk, use batch processing at scheduled intervals.
Fields include location_id, name, address, city, country, and timestamps. You can map these fields from Mailparser outputs to Snapshots. Check field types and ensure data formats match.
API rate limits and docs are available in the Snapshots API reference and the GHL developer docs. Review quotas to plan retries and backoff. If you hit limits, consider batching or scheduling tasks during off-peak hours.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
