Use your API key or OAuth token to securely authenticate requests from Active Knocker to Email API.
Active Knocker stores and rotates credentials to maintain secure connections with Email API.
Endpoints you may use include: POST /users/ for creating users, PUT /users/:userId for updates, DELETE /users/:userId for deletions, GET /workflows/ for listing workflows, and POST courses/courses-exporter/public/import to import courses.
When a new contact is created or updated in Active Knocker, push updates to Email API to keep contact data current.
Actions: create or update a user; assign appropriate onboarding or engagement workflows.
Endpoint: POST /users/ for creation; PUT /users/:userId for updates.
Key fields: email, userId, firstName, lastName.
On user creation, trigger onboarding or engagement workflows in Email API.
Actions: start workflows, assign courses, or send reminders.
Endpoint: GET /workflows/ or POST to start a workflow.
Key fields: workflowId, userId.
When a new course is added in Email API, pull it into Active Knocker or trigger updates accordingly.
Actions: import/export courses, attach to users, and track progress.
Endpoint: POST courses/courses-exporter/public/import
Key fields: courseId, courseName.
Fast setup with no coding required.
Automated data synchronization between Email API and Active Knocker.
Secure, scalable integrations with built-in error handling.
Learn the core terms and processes that power the integration between Email API (GHL) and Active Knocker.
An Application Programming Interface that enables apps to communicate and exchange data.
A specific URL in an API that performs a function.
The method used to verify identity and grant access to resources.
A sequence of automated steps that move data and actions across apps.
Set up a welcome email sequence that triggers after a new user is created, driving engagement.
Trigger campaigns to re-engage inactive users based on activity in Active Knocker.
Send certificates or next-step emails when a course is completed.
Authorize the Email API in Active Knocker and generate an access token.
Select only the endpoints you need (users, workflows, courses) to minimize scope.
Run tests, monitor logs, and push to production.
Email API supports API keys and OAuth tokens. Choose an authentication method that fits your security needs. Store credentials securely in Active Knocker and rotate them regularly. When in doubt, start with a minimal scope and gradually expand permissions as you test the flow.
For user sync, you typically need endpoints to create, update, and delete users, as well as read access for workflows if you want to trigger actions based on user status. Start with POST /users/, PUT /users/:userId, DELETE /users/:userId, and GET /workflows/ for visibility.
Yes. You can import and export course data using the Email API. In Active Knocker, configure a course sync to pull new courses from Email API or push updates to Email API as students progress.
Error handling is built into the connector. If a call fails, Active Knocker can retry, queue, and surface errors in logs. Use status codes to diagnose issues and adjust endpoint permissions as needed.
No coding is required for most integrations. The Zapier App Connector and the Email API connector provide a visual workflow builder. You can map fields, set triggers, and define actions without writing code.
Security is built in: tokens are stored securely, data is transmitted over HTTPS, and access can be scoped to the minimum permissions. Review data policies to ensure compliant handling of personal information.
Logs appear in Active Knocker’s task dashboard. You can filter by date, endpoint, and status. Pair logs with webhook alerts to stay informed about integration health.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
