1. Feature Overview

UDS (Universal Data Sync) includes usage limits and restrictions based on your account’s plan.

This article will help you understand the plan details associated with the Universal Data Sync (UDS) App.

2. UDS Plan Details

To find your UDS plan details, navigate to UDS>Plan Details. All limits applicable to your account will be displayed in this section.

The following table will give a description of each attribute –

FAQs

1. What is a flow?
Please refer to this article: Universal Data Sync (UDS) – Create a Data Flow.

2. Does the maximum flow limit apply across apps?
Yes, the maximum flow limit is shared across all apps.

3. What happens if I reach the maximum number of apps allowed in my plan?
You won’t be able to create additional apps unless you delete an existing one or upgrade your plan.

4. Can I purchase additional plans?
Yes, you can. Please contact your account manager to explore available options. Note that additional charges may apply.

5. Can I delete an app to free up a slot under the maximum apps limit?
Yes, deleting an app will free up a slot for a new one.

6. How many actions can I add before the return response card in a flow?
The number of actions allowed is defined by your plan’s current limits. These limits can be increased by contacting your account manager. Additional charges may apply.

7. What happens if I exceed the allowed number of actions before the return card?
You won’t be able to add more actions beyond the defined limit.

8. Are the return response limits shared across all app flows?
Yes, return response limits are shared across all flows in all apps.

9. What happens if I exceed the daily or 5-second return request limits?
An error will be returned to the API caller. If the limit is breached, the caller will receive a 429 response code, and the request will not be processed.

10. Will flows still run if the return response card limit is hit?
If the return response limit (e.g., number of API calls per day or per 5 seconds) is exceeded, flows will not process the request. A 429 error will be returned to the API caller, and the request will be rejected.

11. What happens if the return response card is disabled?
If disabled, a generic response will be returned instead. In this case, return response limits are not applicable. Actions will be processed in a queued manner.

12. Does hitting the flow or action limits affect already running flows?
No, limits are evaluated when the request is first received. If the request is accepted successfully, it will be processed regardless of subsequent usage limits.

1. Feature Overview

The Return Response action allows UDS workflows to send a custom response back to the API caller. When added, all actions before it run synchronously, while actions after it are queued and processed asynchronously. This is useful when an immediate, dynamic reply is needed.

2. Prerequisites

• You must be an Administrator user, or access must be shared to you by an Admin user
• The Universal Data Sync Connector is a paid feature. To enable it on your account, contact your account manager, or write to support@leadsquared.com.
• Before creating actions, you must select a trigger for your data flow. For more information, see Select a Trigger.
• There are restrictions at the account level for adding a return response card. Please refer to your Plan Details as the following conditions apply –
  • The Return Response card can only be added if it is enabled for the account.
  • The number of actions allowed before the Return Response is also defined at the account level. Only the permitted number of actions can be added before it.
  • Since actions before the return card are executed immediately, a rate limit is enforced to safeguard system performance.

3. Default Behavior Without Return Response Action

If a Return Response card isn’t configured, the following default behavior applies:

1. The request is sent to UDS.
2. UDS queues the request for processing.
3. Based on system bandwidth, queued requests are processed asynchronously.

In such cases, UDS returns a standard response. Here’s an example:

{
"status": "SUCCESS",
"success": true,
"errors": {},
"data": "Request accepted for further processing",
"requestId": "9444df97-0c27-821f-5cc8-ee04ac8c91b7"
}

4. Adding Return Response Actions

All incoming data received on the webhook—including query, body, and headers—as well as the response data from all preceding actions (if response mapping is configured for those actions), can be accessed via the input object in the return response card.

input.<your_action_name> your action response variable data.

4.1 Return Response Action Use case

If an action in UDS creates a lead in LeadSquared, and you want to return the Lead ID from the response of the Lead Create action back to the webhook caller, you can do so using the Return Response card.

Make sure the response mapping is completed for the Lead Create action, so that its output is accessible in the return step via the input object.

How to Configure a Return Response Card

1. Add the Return Response Card

Click + Return on the Actions panel (or use the + icon) to add a Return Response card.

2. Add JavaScript Code

Write the JavaScript code that defines the response you want to send back. By default, a sample snippet is populated when you add the Return card — this returns all the data accessible to the Return Response card.

You can modify this snippet or write your own logic to customize the response.

3. Test with Sample Data

Test your code using sample input data. The input data shown is based on the sample data added during your flow configuration. You can modify the values in this data to test your logic, but:

4. Ensure Test Passes

You cannot save the Return Response card unless the test executes successfully.

5. Save & Close

Once the test passes, click Save & Close to complete the configuration.

With this method, an immediate dynamic response is returned to the user.

5. Using a Response from a Previous Action

You can configure the Return Response Action to use and return data from a previous action in the workflow. This is helpful when your UDS workflow includes intermediate steps such as API calls, data transformations, or lookups, and you want to return only specific data points back to the API caller.

For example, in a workflow with two actions:

1. Fetch Data from a Source – Pulls data based on some predefined logic.
2. Return Response – Sends specific fetched data back to the API caller.

To use the response from a previous action:

• Go to the Return Response card in your workflow.
  • In the Response Configuration section, you can reference the output of a previous action using the syntax: input.<previous_action_name>
  • You can also extract specific fields using dot notation: input.<previous_action_name>.<specific_field_json_path_from_response>
  • Optionally, you can structure the response: {"response": input.<previou_action_name>.<specific_field_json_path_from_response>}

6. Viewing Logs for Return Response Actions

Logs for Return Response Actions can be viewed in the Workflow Logs section of UDS. These logs help you understand how the data flows through the workflow and what is returned to the API caller.

Each execution log shows:

• The input passed to the workflow.
• The response returned by the Return Response action.

Example:

If you passed a name like Pandit Hari Prasad to a workflow with a Split Full Name action followed by a Return Response action:

The Return Response will show the parsed output:

{
"firstName": "Pandit",
"middleName": "Hari",
"lastName": "Prasad"
}

To validate or debug the response:

1. Navigate to the Logs for the specific workflow. You can view logs either from the All Flows page by selecting the flow options and clicking the Logs option, or by opening a specific flow and accessing the Logs tab from within the flow details.
2. Locate the log entry based on the timestamp or request input.
3. Click the icon under WEBHOOK RESPONSE to view the data returned by the Return Response action.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!

1. Feature Overview

The Lead Create action template in Universal Data Sync (UDS) App enables you to create new leads in LeadSquared.

This template leverages the LeadSquared V2 Create a Lead API and eliminates the need for manual API configuration.

2. Use Case

You want to create a lead in LeadSquared for every incoming request.

3. Configure Create a Lead Action

Follow the steps below to configure Create a Lead action –

1. Select Template

Click +Action and choose the Lead Create template.

2. Select Behavior

In this step, the values will be pre-configured as follows:

• Source – LeadSquared
• Entity – Lead
• Action – Lead Create

3. Configure Field Mapping

Map your source fields (from your data source or app) to the appropriate LeadSquared lead fields.

You can do that by selecting the desired Lead fields from the dropdown. Click on + icon, select Entity as Lead, and select the desired field from the dropdown.

For example:

• First Name → lead.FirstName
• Email → lead.EmailAddress
• Phone → lead.Phone
• Custom fields (Such as address proof) → Corresponding custom lead fields

 4. Configure Response Mapping (Optional)

Use this step if you want to:

• Capture the newly created LeadId and pass it to downstream actions.
• Handle API success/failure logic conditionally.

Define the fields you want to extract (e.g., `LeadId`, `Status`, `Message`) and mark what should be considered a successful or failed execution.

FAQs

1. What credentials are used for making API calls via this system?
API calls made through Lead Action template will use system user credential for authentication.

2. Do these API calls count toward any rate limits?

Yes. API calls made via this template are counted against your v2 API usage limits. Specifically:

• Daily Limit: All calls contribute to your daily quota.
• Per 5-Second Limit: Calls also count toward the burst limit of requests allowed every 5 seconds.

3. What happens if I exceed the API rate limits?
If you exceed either the daily or per-5-second limits, further API requests will be rejected until your usage falls within the allowed limits.

4. What are the error scenarios defined
Since we directly call Platform v2 APIs inside the Lead Action template, all standard v2 API error responses will be returned as it is. Refer to the API Reference for error codes.

1. Feature Overview

The Lead Capture action template in Universal Data Sync (UDS) allows you to either create a new lead or update an existing one based on a defined search key.

This template uses the LeadSquared V2 Lead.Capture API, eliminating the need for manual API setup.

2. Use Case

Use this template when you want to:

• Update an existing lead in LeadSquared if it matches a specific field value (such as Email or Phone),
• Or create a new lead if no existing lead is found with that value.

This helps ensure that duplicate leads are not created when the same contact enters the system more than once.

3. Configure Lead Capture Action

1. Select Template

Click +Action and choose the Lead Capture template.

2. Select Behavior

When a lead is found using the search key, use the Capture Behavior setting to define how the existing lead should be updated:

• Do Not Update – The lead will not be modified even if it is found.
• Update Only Empty Fields – Only fields that are currently blank in the lead record will be updated.
• Do Not Update Unique Fields – All fields except those marked as unique will be updated.
• None – No special update rule; the lead will be updated as per the mapped fields.

This setting provides control over how existing data is handled during capture, helping to avoid unwanted overwrites.

3. Configure Field Mapping

Map source fields to LeadSquared lead fields.

You can do that by selecting the desired Lead fields from the dropdown. Click on + icon, select Entity as Lead, and select the desired field from the dropdown.

For example:

• Email → lead.EmailAddress
• Phone → lead.Phone
• Custom fields → relevant lead fields

Specify a search key field (e.g., Email or Phone) that will be used to find existing leads.

4. Configure Response Mapping (Optional)

Capture output fields such as LeadId, Status, or Message. You can also define conditions for success/failure based on API response.

FAQs

1. What credentials are used?
System user credentials are used to make API calls.

2. Are API limits applicable?
Yes. These calls are counted toward your LeadSquared V2 API limits (daily and 5-second burst).

3. What happens if limits are exceeded?
API requests will be rejected until your usage is back within limits.

4. What errors should I expect?
Standard V2 API errors will be returned. See the LeadSquared V2 API Reference for details.