Scenario
A company uses an external CRM (like Zoho CRM or Salesforce) to collect leads. Whenever a lead qualifies, the CRM needs to automatically create a task card in Qntrl's process management system to trigger internal follow-up actions. Instead of manually creating a task in Qntrl, the external system can call an Inbound REST API in Qntrl to automate this.
How It Works
CRM sends a POST request to Qntrl’s Inbound REST API.
This API is configured in Qntrl to receive the data and create a card in a workflow (e.g., Sales Follow-up).
The API passes lead information like name, email, and interest level to Qntrl.
A Function in Qntrl handles the data and creates the card with the right details and assignments.
The operations team gets notified and can immediately take action.
Business Impact
✅ Faster Lead Handling: No need for manual task creation — cards appear instantly.
✅ Error-Free Task Creation: Ensures lead data is passed accurately from CRM to Qntrl.
✅ Saves Time: Automates routine steps, letting teams focus on important tasks.
✅ Improves Coordination: Sales and operations stay in sync with real-time updates.
✅ Scalable and Secure: Handles high volumes and supports authentication with tokens or OAuth.
Create a Module
Each set of related APIs must belong to a module.
Navigate to
(
settings)
>> WEB SERVICES >> Inbound >> Select REST. Click New Inbound REST.
Fill in:
Click Create.
Once the module is created, a configuration window will open to define the API endpoint.
Name: Create Card
URL: /create
Method: POST
Resource Type: Function
Resource: Choose or create a function to handle card creation logic using input parameters.
lead_name (String, Mandatory)
email (String, Regex validation, Mandatory)
priority (String, Optional)
{
"lead_name": "Alice",
"email": "alice@company.com",
"priority": "High"
}
Click Save to complete the configuration.
Save and Publish
Click Save to make the endpoint live.
Share the endpoint and authentication token with the CRM system.
The CRM can now send HTTP POST requests to:
https://<your-org>.qntrl.com/webservice/<org-id>/lead/create
Example Use in a CRM
Here’s an example of how to send an inbound REST request from your CRM to Qntrl using the POST method with a JSON payload.
Endpoint:
POST https://<org>.qntrl.com/webservice/668909960/lead/create
Headers:
Content-Type: application/json
X-CRM-Auth: your-api-key
Body:
Related Articles
Automate transitions
Using Qntrl, you can configure transitions to be executed automatically by setting a wait time or a condition. Automate by time Transitions can be configured to execute automatically after a specific time frame. Navigate to Boards , hover over any ...
Manage Business Rules
What is a business rule? A business rule helps you trigger an event or a chain of automated events, when a defined action occurs in a card. For example, when a card's assignee field is updated, you might want to change the card's supervisor field ...
Connected and Standalone Cards
In an integrated workspace where different teams collaborate on tasks, they might encounter situations where follow-up tasks are to be created from the main task for other teams to work on. For example, in a food delivery app, once the customer ...
Business Case: Automating Vendor Invoice Validation with External ERP
Scenario A company is looking to simplify and automate its vendor invoice processing. The finance team receives invoices from various vendors daily. Each time a new invoice is submitted in Qntrl, the system needs to validate invoice must be validated ...
Card Lock
Card lock allows you to restrict users from editing the entire card or specific fields of the card. Using card lock you can: Lock the entire card Lock all the fields Lock attachments Lock comments Disable lock Card lock can be configured in the After ...