LeadSquared

LeadSquared assigns each account to a regional data center, and the API host varies by region. The default host is https://api.leadsquared.com, but Indian accounts typically use https://api.in21.leadsquared.com, and other regions may use different subdomains. Using the wrong host is the most common cause of authentication errors — you get a generic host/auth failure rather than a clear 'wrong host' message. To find your correct host: log into your LeadSquared dashboard and go to Settings (gear icon) → API and Webhooks. The page will display your Access Key, Secret Key, and the API host for your account. Copy all three values. The Access Key is a long alphanumeric string (similar to a username) and the Secret Key is a longer hex string (similar to a password). Both are required on every API call. Do not store these credentials anywhere in your FlutterFlow project — not in App Values, not in App State, not hardcoded in Custom Actions. They will go into a Firebase Cloud Function environment variable in the next step, where they remain server-side and out of the compiled app bundle. If you accidentally commit them to a GitHub repo or expose them in a FlutterFlow API Call, rotate them immediately from Settings → API and Webhooks → Regenerate. Also note your LeadSquared account's time zone and date format, as some activity logging endpoints require dates in a specific format (ISO 8601 or YYYY-MM-DD HH:mm:ss). Getting this wrong doesn't break lead capture but causes activity timestamps to appear incorrect in the CRM.

Create a Firebase HTTPS Cloud Function that acts as a secure proxy between FlutterFlow and LeadSquared. The function receives lead field data (name, email, phone, source, and any custom fields) from FlutterFlow as a JSON POST body, then constructs the URL to the LeadSquared Lead.Capture endpoint with the Access Key and Secret Key appended as query parameters, and forwards the lead data as the POST body. Store the LeadSquared credentials as Firebase Cloud Function secrets using the Firebase Functions config system or Secret Manager. In the function code, build the full LeadSquared URL by appending ?accessKey=VALUE&secretKey=VALUE to the endpoint path. Never hardcode the key values in the function source code — always read them from environment secrets so that your source code repository does not contain credentials. The Lead.Capture endpoint (POST /v2/LeadManagement.svc/Lead.Capture) accepts an array of lead field objects, each with Attribute (field name) and Value. Map the form fields from your FlutterFlow form to LeadSquared's standard attributes: FirstName, LastName, EmailAddress, Phone, Source, LeadQuality, and any custom fields your account uses. The response from LeadSquared includes a Status ('Success' or error) and the LeadId of the created or updated lead (Lead.Capture upserts on matching email or phone — if a lead with the same email already exists, it updates that record rather than creating a duplicate). Return the lead ID from the Cloud Function back to FlutterFlow so you can store it for subsequent activity logging. Deploy the function and test it by calling it directly with a curl command or Postman before wiring it to FlutterFlow.

1// Firebase Cloud Functions v2 — LeadSquared Lead.Capture proxy (index.js)
2const { onRequest } = require('firebase-functions/v2/https');
3const { defineSecret } = require('firebase-functions/params');
4const cors = require('cors')({ origin: true });
5const fetch = require('node-fetch');
6
7const LS_ACCESS_KEY = defineSecret('LEADSQUARED_ACCESS_KEY');
8const LS_SECRET_KEY = defineSecret('LEADSQUARED_SECRET_KEY');
9// Set your region host here — update to api.in21.leadsquared.com for India accounts
10const LS_HOST = 'https://api.leadsquared.com';
11
12exports.captureLeadSquaredLead = onRequest(
13  { secrets: [LS_ACCESS_KEY, LS_SECRET_KEY] },
14  async (req, res) => {
15    cors(req, res, async () => {
16      if (req.method !== 'POST') {
17        return res.status(405).json({ error: 'Method not allowed' });
18      }
19      const { firstName, lastName, email, phone, source, customFields } = req.body;
20
21      // Build the lead attributes array expected by LeadSquared
22      const leadAttributes = [
23        { Attribute: 'FirstName', Value: firstName || '' },
24        { Attribute: 'LastName', Value: lastName || '' },
25        { Attribute: 'EmailAddress', Value: email || '' },
26        { Attribute: 'Phone', Value: phone || '' },
27        { Attribute: 'Source', Value: source || 'Mobile App' },
28      ];
29
30      // Merge any custom fields passed from FlutterFlow
31      if (customFields && Array.isArray(customFields)) {
32        leadAttributes.push(...customFields);
33      }
34
35      const url =
36        `${LS_HOST}/v2/LeadManagement.svc/Lead.Capture` +
37        `?accessKey=${LS_ACCESS_KEY.value()}&secretKey=${LS_SECRET_KEY.value()}`;
38
39      try {
40        const response = await fetch(url, {
41          method: 'POST',
42          headers: { 'Content-Type': 'application/json' },
43          body: JSON.stringify(leadAttributes),
44        });
45        const data = await response.json();
46        if (!response.ok || data.Status !== 'Success') {
47          return res.status(400).json({ error: data });
48        }
49        return res.json({ leadId: data.LeadId, status: data.Status });
50      } catch (err) {
51        return res.status(500).json({ error: err.message });
52      }
53    });
54  }
55);

In FlutterFlow, design the lead capture form on your target page. Use Text Field widgets for name, email, phone, and any other required fields. Set each Text Field to be bound to a Page State variable: create Page State variables (under State Management in the left panel) for each field — firstName (String), lastName (String), emailAddress (String), phone (String), and any custom fields you need. For validation: add a Form widget as a wrapper (from the widget library) and mark EmailAddress as 'Email' type (triggers basic email format validation) and Phone as 'Phone' type. Add a Validate Form action to the submit button's Action Flow so users see inline errors before the API call fires. Wire the submit button to an Action Flow with these steps: (1) Validate Form — if invalid, stop. (2) Show Loading Indicator (set a Boolean Page State variable isSubmitting to true and show a CircularProgressIndicator overlay). (3) Call the API Action for the Cloud Function (configured in the next step). (4) On success, store the returned leadId in a persistent App State variable or write it to Firestore alongside the user's profile. (5) Navigate to a thank-you page or show a SnackBar. (6) Always turn off the loading indicator in both success and error branches. Also consider adding a hidden 'Source' field that automatically captures where in the app the lead came from (e.g. 'Homepage CTA', 'Pricing Screen', 'Feature Tour') — this is extremely valuable for LeadSquared analytics and lead scoring, and costs nothing extra to send. You can hardcode the source value per page rather than making it a user-visible field.

In FlutterFlow, click API Calls in the left navigation sidebar, then click + Add → Create API Group. Name it 'LeadSquaredProxy' and set the base URL to your Firebase Cloud Function's base HTTPS URL (e.g. https://us-central1-yourproject.cloudfunctions.net). This points to your Cloud Function, NOT to LeadSquared's API directly — the Cloud Function handles the key appending and forwarding. Inside the API Group, click + Add API Call. Name it 'CaptureLead'. Set the method to POST and the endpoint to /captureLeadSquaredLead (matching your function name exactly). In the Body tab, select JSON format and add the fields your form collects: { "firstName": "{{ firstName }}", "lastName": "{{ lastName }}", "email": "{{ emailAddress }}", "phone": "{{ phone }}", "source": "{{ source }}" }. In the Variables tab, add variables for each field (all String type). Set the Content-Type header to application/json. You do NOT need any Authorization header or API keys in FlutterFlow — all credentials live in the Cloud Function. Click Test in the Response & Test tab. Enter sample values and fire the call. Paste the sample success response and click Generate JSON Paths. Map $.leadId as a JSON Path extraction so you can store the lead ID after a successful call. Now go back to your form page and update the submit button's Action Flow: after validation, add a Backend/API Call action pointing to the CaptureLead API Call, passing the Page State variables as the API Call variables. Add a conditional after it: if $.leadId is not empty → store the leadId in App State and navigate to success screen. If the call returned an error → show a SnackBar with an error message.

1// FlutterFlow API Call config reference
2// API Group: LeadSquaredProxy
3// Base URL: https://us-central1-yourproject.cloudfunctions.net
4// (Replace with your actual Cloud Function project and region)
5//
6// API Call: CaptureLead
7// Method: POST
8// Endpoint: /captureLeadSquaredLead
9// Headers: Content-Type: application/json
10// (No Authorization header needed — keys are in the Cloud Function)
11//
12// Body (JSON):
13// {
14//   "firstName": "{{ firstName }}",
15//   "lastName": "{{ lastName }}",
16//   "email": "{{ emailAddress }}",
17//   "phone": "{{ phone }}",
18//   "source": "{{ source }}"
19// }
20//
21// Response JSON Paths:
22// $.leadId  → leadId (String)
23// $.status  → leadStatus (String)

After a successful lead capture, the Cloud Function returns the LeadSquared leadId (a unique identifier for the lead record). Store this in FlutterFlow's App State (for the current session) and optionally in Firestore alongside the user's UID if your app has authentication. This ID is what you use to log future activities against the lead — without it, activity calls will create orphaned records or fail. Activity logging is the second high-value use of the LeadSquared API. If your app has meaningful user actions (completed a quiz, viewed a pricing screen, started a free trial, booked a demo), logging these as LeadSquared activities gives the sales team a timeline of engagement in their CRM. The endpoint is POST /v2/LeadManagement.svc/Activity.Create and it requires the leadId, an activityCode (a numeric ID for the activity type defined in LeadSquared), a note, and a timestamp. Activity type codes are account-specific and not globally standardized — a code that means 'Viewed Pricing' in one account might mean something else in another. Never hardcode these numeric codes. Instead, deploy a second Cloud Function (or add a route to the existing function) that calls GET /v2/LeadManagement.svc/Lead.GetActivityTypes.GetAll to fetch all activity types and their codes, then cache the response in Firestore or App State. Refresh this cache periodically or on app startup. For a simpler first implementation: build the activity logging as a second API Call in FlutterFlow pointing to a /logLeadActivity endpoint on your Cloud Function. Pass the leadId from App State, the activity code (fetched dynamically), a note, and the current timestamp. Call this from key page Action Flows: on navigating to the pricing page, on completing an onboarding step, on booking a consultation. This transforms your app from a simple lead capture form into a full sales intelligence tool.

1// Firebase Cloud Function — activity logging route (add to index.js)
2const LS_ACCESS_KEY = defineSecret('LEADSQUARED_ACCESS_KEY');
3const LS_SECRET_KEY = defineSecret('LEADSQUARED_SECRET_KEY');
4const LS_HOST = 'https://api.leadsquared.com'; // update per region
5
6exports.logLeadActivity = onRequest(
7  { secrets: [LS_ACCESS_KEY, LS_SECRET_KEY] },
8  async (req, res) => {
9    cors(req, res, async () => {
10      if (req.method !== 'POST') return res.status(405).send('Method not allowed');
11      const { leadId, activityCode, note } = req.body;
12      if (!leadId || !activityCode) {
13        return res.status(400).json({ error: 'leadId and activityCode are required' });
14      }
15      const now = new Date().toISOString().replace('T', ' ').substring(0, 19);
16      const payload = [
17        {
18          LeadId: leadId,
19          ActivityEvent: activityCode,
20          ActivityNote: note || '',
21          ActivityDateTime: now,
22        },
23      ];
24      const url =
25        `${LS_HOST}/v2/LeadManagement.svc/Activity.Create` +
26        `?accessKey=${LS_ACCESS_KEY.value()}&secretKey=${LS_SECRET_KEY.value()}`;
27      try {
28        const response = await fetch(url, {
29          method: 'POST',
30          headers: { 'Content-Type': 'application/json' },
31          body: JSON.stringify(payload),
32        });
33        const data = await response.json();
34        return res.json(data);
35      } catch (err) {
36        return res.status(500).json({ error: err.message });
37      }
38    });
39  }
40);