Establish credentials, set required scopes, and generate API keys to authorize requests from 17hats to the Memberships API.
In the 17hats integration, use OAuth 2.0 or API keys to authorize requests to the Memberships API, ensuring secure data flow.
Available endpoints: GET /users/; GET /users/{userId}; additional endpoints are defined in the API docs and may be enabled as needed.
Triggered when a new user is created in the Memberships API to create or update the corresponding contact in 17hats.
Actions: Create or update a contact in 17hats, sync membership status, and apply relevant tags.
GET /users/
email, first_name, last_name, membership_status, id
Triggered when a membership status changes in the Memberships API to update the linked contact in 17hats.
Actions: Update contact fields in 17hats (status, tier), add notes, and trigger follow‑up tasks.
GET /users/{userId}
email, membership_status, last_updated
Triggered when a new user is created in the Memberships API to create a new contact in 17hats.
Actions: Create contact in 17hats, set default membership tier, and organize tagging.
POST /users
email, first_name, last_name, membership_type
Automate onboarding and membership provisioning without writing code.
Keep contact data synchronized in real time across systems.
Segment members easily and trigger targeted campaigns from 17hats.
This section defines endpoints, triggers, actions, and data mappings used to connect the Memberships API with 17hats.
A specific URL path that lets you access resources in the Memberships API.
A secure authorization framework used to grant limited access to an API without sharing credentials.
A token used to authenticate requests to the Memberships API.
A callback URL that the API uses to send real-time event updates.
Set up a flow that automatically creates a 17hats contact when a new Membership is added, and assigns an onboarding task.
Trigger renewal reminders in 17hats based on Memberships API renewal dates.
Create segmentation rules in 17hats based on membership type, status, and activity in the Memberships API.
Obtain OAuth credentials or API keys and authorize the integration between the Memberships API and 17hats.
Map contact and membership fields between the two systems to ensure accurate data transfer.
Turn on triggers and run end‑to‑end tests to verify data flows.
No coding is required for standard connections. Use the Zapier App Connector to create triggers and actions. For advanced mappings, you can tailor which fields move between Memberships API and 17hats. See the docs or contact support for help.
At minimum, you need the authenticated endpoints for /users and a user identifier (/users/{userId}). The setup guide covers initial field mappings and testing steps.
The connection uses OAuth 2.0 or API keys over HTTPS. Secrets are stored securely and access is scoped. You can enable IP whitelisting for extra security.
Yes. Use Zapier’s test mode or sandbox endpoints where available to validate data flows without affecting live data. Run end-to-end tests with mock data.
Yes. You can map custom fields from Memberships API to corresponding fields in 17hats. Use a mapping template to keep fields aligned and consistent.
If an API call fails, the connector will retry with exponential backoff. Configure retry rules and alerting in Zapier to handle persistent issues.
Rate limits depend on your plan; check the API docs for quotas. If you anticipate bursts, implement throttling in your workflows or upgrade to higher capacity.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
