How to Integrate Retool with LeadSquared

Log in to your LeadSquared account. Navigate to Settings by clicking the gear icon or your profile in the top-right corner and selecting Settings. In the Settings menu, look for the 'API & Webhooks' or 'Developer' section in the left sidebar — the exact label may vary slightly by LeadSquared version. On the API settings page, you will find two key credentials: the Access Key (a shorter alphanumeric identifier) and the Secret Key (a longer alphanumeric secret). Both are required for every API request. Copy both values and store them securely. Also note your API host URL on this page — LeadSquared uses region-specific API endpoints. The standard URL for most accounts is https://api.leadsquared.com, but accounts in India (IN region) may use https://api.in21.leadsquared.com or a similar regional subdomain. This host URL forms the base of your Retool resource configuration. The access key and secret key are passed as query parameters (not headers) on every API request: ?accessKey=YOUR_KEY&secretKey=YOUR_SECRET. This is important to note because Retool handles header-based auth differently from query-parameter-based auth — you will configure these as default URL parameters in the Resource.

In Retool, navigate to the Resources tab in the left sidebar and click Add Resource. Select REST API from the resource type list. Name the resource 'LeadSquared'. In the Base URL field, enter your LeadSquared API host URL in the format https://api.leadsquared.com — substitute the regional variant if your account uses a different host. Do not include a trailing slash. Scroll to the URL Parameters section (not Headers — LeadSquared uses query parameters for auth). Add two default URL parameters that will be appended to every query automatically. First parameter: key set to 'accessKey' and value set to your LeadSquared Access Key. Second parameter: key set to 'secretKey' and value set to your LeadSquared Secret Key. These parameters will be sent on every request to the resource without needing to include them in individual query configurations. Alternatively, if you prefer to use Retool's Configuration Variables (more secure — recommended), store the keys as config vars named LEADSQUARED_ACCESS_KEY and LEADSQUARED_SECRET_KEY, then set the URL parameter values to {{ retoolContext.configVars.LEADSQUARED_ACCESS_KEY }} and {{ retoolContext.configVars.LEADSQUARED_SECRET_KEY }} respectively. Add a Content-Type header with value application/json for POST request bodies. Click Save Changes. To verify the configuration, create a test query with GET method and path /v2/LeadManagement.svc/Leads.Get?fetchSize=5 — a successful response returns the first 5 leads in your account.

Create a new query named 'getLeads' in your Retool app's Code panel. Select your LeadSquared resource. Set Method to GET and Path to /v2/LeadManagement.svc/Leads.Get. LeadSquared's lead retrieval endpoint supports filtering via URL parameters. In the URL Parameters section of the query, add: 'fetchSize' set to {{ pagination.pageSize || 25 }} for results per page, 'pageIndex' set to {{ pagination.page - 1 || 0 }} for zero-indexed pagination, and optionally 'score_min' bound to {{ scoreFilter.minValue || 0 }} and 'score_max' bound to {{ scoreFilter.maxValue || 100 }} for score-based filtering. For more specific filtering, LeadSquared uses a different approach: the SearchLeads endpoint at /v2/LeadManagement.svc/Leads.GetByField requires a JSON body with the search criteria. Create a separate query named 'searchLeads' for this purpose with POST method, Path /v2/LeadManagement.svc/Leads.GetByField, Body Type JSON, and a body containing the search field and value. LeadSquared's API returns lead data in a different structure than typical REST APIs — responses include a Status field ('Success' or 'Error') and a Leads array (for list endpoints) or a Lead object (for single record endpoints). Add a transformer to check the Status field and extract the Leads array, mapping each lead to table-friendly fields.

1// Transformer: flatten LeadSquared leads response
2if (data.Status !== 'Success') {
3  console.log('LeadSquared API error:', data.Message || data.Status);
4  return [];
5}
6const leads = data.Leads || data.Lead || [];
7const leadsArray = Array.isArray(leads) ? leads : [leads];
8return leadsArray.map(lead => {
9  const attrs = {};
10  (lead.LeadPropertyList || []).forEach(prop => {
11    attrs[prop.Attribute] = prop.Value;
12  });
13  return {
14    id: lead.LeadId || attrs.LeadId || '',
15    name: attrs.FirstName ? `${attrs.FirstName} ${attrs.LastName || ''}`.trim() : attrs.Email,
16    email: attrs.EmailAddress || attrs.Email || '',
17    phone: attrs.Phone || attrs.Mobile || '',
18    source: attrs.Source || '',
19    stage: attrs.LeadStage || '',
20    score: parseInt(attrs.LeadScore || '0'),
21    owner: attrs.OwnerId || '',
22    created: attrs.CreatedOn ? new Date(attrs.CreatedOn).toLocaleDateString() : '',
23    last_activity: attrs.LastActivityDate ? new Date(attrs.LastActivityDate).toLocaleDateString() : 'None'
24  };
25});

In the Retool canvas, add a metrics row at the top with three Statistic components: Total Leads (count from getLeads.data), Average Lead Score (computed average), and Leads with No Activity in 7+ Days (filtered count). Below metrics, add filter controls: a Select for lead stage (populated by a query to GET /v2/LeadManagement.svc/LeadStages.Get), a Select for owner/rep (populated by a users query), and a Range Slider for score filtering (0-100, named 'scoreFilter'). Add a Table component bound to {{ getLeads.data }} with columns configured as: name, email, phone, source, stage (with conditional formatting for color — green for hot stages, yellow for nurture, gray for unqualified), score (numeric with bar visualization), owner, last_activity. Sort the default view by score descending so highest-priority leads appear first. Create a lead detail side panel: when a table row is selected, load the full lead record using a query named 'getLeadDetail' at GET /v2/LeadManagement.svc/Leads.GetById?Id={{ leadsTable.selectedRow.id }}. Show the lead's complete attribute list in the detail panel using Retool's Key-Value component. Below the key-value display, add a Log Activity form with a Select for activity type (Call, Email, Note, Appointment), a Multiline Text Input for notes, and a Submit button that posts to LeadSquared's activity creation endpoint. Add a stage progression button that fires a PATCH or PUT request to update the lead's stage.

1// POST body for Log Activity query
2{
3  "LeadId": "{{ leadsTable.selectedRow.id }}",
4  "Activity": {
5    "ActivityEvent": 206,
6    "ActivityNote": "{{ activityNote.value }}",
7    "ActivityType": "{{ activityType.value }}"
8  }
9}

Create a query named 'getLeadActivities' with GET method and path /v2/ProspectActivity.svc/GetAll?leadId={{ leadsTable.selectedRow.id }}&pageIndex=0&pageSize=50. This returns all activities logged for the selected lead in reverse chronological order — including emails, calls, form submissions, website visits, and manual notes. Add a transformer to extract activity type, date, note content, and the user who performed the action into table rows. Display this in a Timeline-style Table component within the lead detail panel, sorted by date descending. For pipeline analytics, create a query named 'getPipelineStats' that fetches opportunities or leads grouped by stage. Use a POST to /v2/LeadManagement.svc/Leads.GetByStages or a similar analytics endpoint, or use the Leads.Get endpoint with stage filter and combine multiple queries with different stage values using a JavaScript query that calls all stage queries in parallel and merges results. Display the pipeline data as a Funnel or Bar Chart showing lead count and total value by stage. Add a date range filter to scope the pipeline view to leads created within a specific period. Build a Tab component with three tabs: Leads (the main management table), Activity (for the selected lead's timeline), and Pipeline (for the funnel chart). For complex multi-team LeadSquared deployments with custom fields, lead scoring rules, and automated activity Workflows, RapidDev's team can help architect your Retool sales operations solution.

1// Transformer: flatten LeadSquared activities response
2if (data.Status !== 'Success') return [];
3const activities = data.ProspectActivities || [];
4return activities.map(activity => ({
5  id: activity.Id,
6  type: activity.ActivityType || 'Activity',
7  date: activity.ActivityDate ? new Date(activity.ActivityDate).toLocaleString() : '',
8  note: activity.ActivityNote || '',
9  event_code: activity.ActivityEvent || 0,
10  performed_by: activity.PerformedByUserId || '',
11  related_to: activity.RelatedEntityName || ''
12}));