Authenticate requests with your Email API credentials. Include the API key in the Authorization header as a Bearer token and ensure the scope users.write is granted.
Connect 17hats using OAuth or a secure API token. Store credentials securely and follow least privilege access.
POST /users/; DELETE /users/:userId; PUT /users/:userId; workflows.readonly; GET /workflows/; courses.write; POST courses/courses-exporter/public/import; Additional endpoints are available as needed.
Trigger: a new contact is created in Email API
Actions: create a new 17hats contact, set default lead status, and assign to a pipeline
POST /users/
name, email, phone, company
Trigger: contact details updated in Email API
Actions: update the corresponding 17hats contact fields
PUT /users/:userId
userId, email, updatedFields
Trigger: contact deletion or inactivation in Email API
Actions: delete the 17hats contact and remove it from lists
DELETE /users/:userId
userId, email
No code data syncing from Email API to 17hats saves time and reduces manual entry
Automations run in the background, increasing accuracy and speed
Scalable, repeatable workflows that scale with your business
This glossary covers endpoints, triggers, actions, key fields, and workflows used to connect Email API with 17hats.
An interface that allows applications to talk to each other.
A specific URL that performs a defined operation in an API.
A real time notification mechanism from one app to another.
Proof of identity for API access, typically via API keys or OAuth tokens.
When a new client is added in 17hats, trigger an onboarding email via Email API.
Use 17hats events to drive targeted email campaigns through Email API.
Bidirectional sync ensures contact updates reflect in both apps.
Obtain an API key and grant the necessary scope (users.write), then store securely.
Connect the endpoints listed above and map Email API fields to 17hats fields.
Run test triggers, verify data accuracy, and set up alerts.
You can set up this integration without writing code using standard webhooks and the Email API connectors. Start by authenticating and mapping fields between Email API and 17hats. Then configure triggers to push data to 17hats automatically. If you need custom behavior, use builder tools to assemble multi-step workflows.
Email API can trigger on new or updated contacts, campaigns, and workflow events. You can wire these triggers to create, update, or delete corresponding records in 17hats. Always test events in a staging environment first.
Yes. You can map custom fields from Email API to corresponding fields in 17hats and use conditional logic in your workflows to route data based on field values.
Yes. Real time webhooks push changes as they happen. You can also run periodic syncs as a fallback to ensure data consistency.
Use API keys and OAuth tokens for authentication. For Email API requests, include Bearer tokens in the Authorization header and ensure the required scopes are granted. For 17hats, follow their token or OAuth procedure.
Create test contacts and test triggers in a safe environment. Verify field mappings, run end to end tests, and monitor logs for any errors. Adjust configurations as needed.
API documentation is available in the GHL developer portal and in 17hats developers docs. Use the shared endpoints list and code samples to implement your integration.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
