Use the Email API access token and Rankr credentials to securely authorize requests. Ensure the scope users.write is granted.
Rankr uses OAuth 2.0 with a client ID and client secret. Request the users.write scope to issue commands to Email API.
POST /users/ creates users in Email API. DELETE /users/:userId removes a user. PUT /users/:userId updates a user. GET /workflows/ lists workflows for automation. POST courses/courses-exporter/public/import imports course data.
Trigger a new Rankr user event to create a corresponding Email API user with POST /users/
Actions include assigning initial role, linking the profile and enabling email sends
POST /users/
Key fields include email, fullName and role
Trigger Rankr user deletion to remove the Email API user with DELETE /users/:userId
Actions deactivate the user, revoke access and archive history
DELETE /users/:userId
Key fields include userId
Trigger a workflow from Email API using GET /workflows/ to start Rankr automation
Actions run Rankr workflows and update status in both systems
GET /workflows/
Key fields include workflowId and name
No code integration using API endpoints and webhooks enables fast setup
Prototyping is faster with visual triggers and actions in ActiveDEMAND
Maintenance is easier with centralized configuration in the integration
This section defines endpoints, triggers, actions, authentication and data fields used in the integration
A specific URL and HTTP method used to interact with an API
A real time notification sent by a service to another app
Process to verify identity before granting access
A sequence of automated steps including triggers and actions
Trigger a welcome email and create the Email API user on Rankr signup
Unified cross system status dashboard
Automated reengagement when users become inactive
Obtain API keys and grant consent
Set up rank based triggers and Email API actions
Run test transactions and verify results
To authenticate, generate an Email API key from the Email API dashboard and configure OAuth for Rankr. Use the key in the Authorization header as a bearer token. Ensure the access token has the users.write scope to perform create and update actions.
The integration relies on a subset of endpoints such as POST /users/ for creating users, PUT /users/:userId and DELETE /users/:userId for updates and removals, and GET /workflows/ for retrieving workflows. You can test these in a sandbox environment before going live. The endpoint list helps map triggers to actions in Rankr.
Yes you can test with sandbox data. Create test accounts in Email API and Rankr and simulate user creation, updates, and workflow runs. Use test endpoints and fake data to verify behavior without impacting real users.
Rate limits depend on your Email API plan. Typical limits are per minute or per hour based on the tier. Monitor headers and the dashboard to avoid hitting caps and to plan retries.
No code options exist through the ActiveDEMAND integration. You can build powerful automations with triggers and actions without writing code. This is ideal for rapid deployment.
Error responses include HTTP status codes and descriptive messages. Use retries with exponential backoff and keep logs for debugging. Implement proper error handling in your workflow.
To revoke access, remove the OAuth tokens and revoke API keys in both Email API and Rankr. Update your credentials and reauthorize connections if needed.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
