Skip to main content
IndeCx is a customer engagement platform that helps businesses manage and optimize their customer interactions and data. It provides tools for customer data integration, enabling companies to streamline their customer relationship management processes.

​
Configuring IndeCx as a Destination

In the Destinations tab, click on the “Add destination” button located on the top right of your screen. Then, select the IndeCx option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide your IndeCx API credentials for authentication with their v3 integration API. The following configurations are available:
  • Company Key: Your Company Key for authenticating with the IndeCx API. This key is used to obtain access tokens for secure API communication.
  • Action Identifier: The Action Identifier used to specify the integration endpoint in the IndeCx API.
If you don’t know where to find your Company Key and Action Identifier, check the IndeCx API documentation or reach out to your IndeCx account manager.
Once you’re done, click Next.

​
2. Select your data to send

Choose which data you want to send to IndeCx. Select the layer and then the desired table.
The table can be found more easily by typing its name.
Select your data and click Next.

​
3. Map your data fields

Configure how the fields from your source table should be mapped to the fields in the IndeCx API payload. Below are the available fields you can map your data to:
FieldTypeDescription
nomeStringThe customer’s name.
emailStringThe customer’s email address.
telefoneStringThe customer’s phone number.
At least one of telefone or email must be provided.
Once you’ve mapped your fields, click Next.

​
4. Configure data destination

Describe your destination for easy identification within your organization, not exceeding 140 characters. Include details like what data it contains and which team it belongs to. To define your Trigger, consider how frequently you need the data updated in IndeCx. Common choices include:
  • Daily: For regular customer data updates
  • Weekly: For less frequent synchronization needs
  • Real-time: For immediate data availability requirements
Optionally, you can configure additional settings:
  • Configure Delta Log Retention to determine how long to store old states of synchronized data. Read more about this resource here.
Once you are ready, click Next to finalize the setup.

​
5. Check your new destination

Once completed, you’ll receive confirmation that your new destination is set up successfully! You can view your new destination on the Destinations page. To see the data in IndeCx, wait for the pipeline to run or manually trigger it by clicking the refresh icon. Monitor execution status on the Destinations page.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!

​
Implementation Notes

​
Authentication & Security

  • The connector uses IndeCx’s v3 API with token-based authentication
  • Access tokens are automatically refreshed every 30 minutes to maintain secure connections
  • Authentication tokens are cached and reused until near expiration to optimize API calls

​
Data Processing

  • Data is sent to IndeCx in batches of up to 1,000 records at a time for optimal performance
  • The connector automatically handles rate limiting and retries failed requests
  • All customer data is validated before transmission to ensure API compatibility

​
API Limitations

  • Rate Limiting: The IndeCx API may apply rate limits during high-volume operations
  • Batch Size: Maximum of 1,000 records per API request
  • Required Fields: At least one contact method (email or telefone) must be provided for each record
  • Authentication: Access tokens expire every 30 minutes and are automatically renewed