Symptoms
Customers have their preferred marketing apps and systems to communicate with Invoca call data. However, the system is not listed in the tiles on the platform’s integrations page.Resolution
Invoca offers support for a wide range of integrations, enabling the sharing of call data with other marketing/sales management services. With these integrations, customers can maximize the effectiveness and utilization of call data.While Invoca provides extensive integration support, certain platform limitations may prevent it from supporting specific integrations. In such cases, there are alternative workarounds to facilitate the sharing of Invoca call data with external systems.
Additional Information
1. Custom WebhooksCustomers can build custom webhooks in the platform to transmit Invoca call data to external systems.
Customers can specify the desired data to be sent, firing conditions, and authentication parameters within the webhook configuration. It is essential to determine the specific API endpoint to establish the connection.
The familiarity with API endpoints and the required data for the system may necessitate assistance from developer resources.
2. Invoca APIs
If customers have a developer resource well-versed in REST APIs and skilled in constructing API requests, leveraging the Invoca APIs can be a viable choice.
The Invoca Developer Portal page offers a range of APIs in order to retrieve, transmit, and modify Invoca data, granting customers complete control over when to perform these actions.
As APIs require authentication, acquiring the API credentials from the platform and including them as parameters becomes necessary.
- Network API - Get, Post, Modify, and Delete data
- To access the data linked to networks, including campaigns, profiles (advertisers), promotional numbers, and more.
- Transactions API - Get data
- To receive call data within the network, granting you the flexibility to include various options and parameters to retrieve specific data of your choice.
- Signal API - Post data
- To incorporate Signals and/or Marketing Data Fields from other systems into specific calls within Invoca. Applying this functionality can enrich the Invoca data with additional details post-call.
3. SFTP for Data Deliveries and Signal File Upload
If customers lack developer resources to configure API requests, data transfer via FTP/SFTP can be an alternative. This method can be utilized to retrieve Invoca data, allowing customers to transmit it to external systems or send Signals or Marketing Data Fields from external systems to Invoca.
- Data Deliveries
- Customers can set up a regular Invoca call report delivered daily, weekly, or monthly using FTP/SFTP set by either customer or Invoca (SSH key is supported.)
- Reports can also be sent to customers’ Amazon S3 buckets.
- Signal File Upload
- Customers can transmit the file to an SFTP server designated by either the customer or Invoca. This enables Invoca to conduct routine file scanning and efficiently process the data, seamlessly integrating it into Invoca's call data. (SSH key is NOT supported.)
4. Signal File Upload
Customers can easily upload files onto the platform to apply Signals and/or Marketing Data Fields from an external system to their Invoca call data, resulting in enhanced call data. The process is user-friendly and does not require any technical skills.
