Connect inTouch to your systems using APIs and integrations
Enable communications, synchronise data and receive events from CRM systems, e-commerce platforms, business management systems and applications. Use APIs, webhooks and connectors to integrate messaging into the processes you already use.
Communications are based on the data and events you already have
An order changes status, a contact is created, an appointment is approaching, or a login requires verification. The integration links these events to the rdcom services, so that communication can be initiated from within the process without requiring any manual intervention or unnecessarily duplicating data.
Event in the system
- New order or change of status
- New contact or qualified lead
- Appointment or deadline
- Sensitive access or operation
- Delivery or interaction outcome
Communication is possible
- Confirmation, update, availability or delivery.
- Welcome, follow-up or transition to a Journey.
- Reminder, change, confirmation or renewal.
- OTP or process-defined verification.
- Updating the CRM or triggering a follow-up action.
Choose the level of integration best suited to your project
When control, application logic and the structured exchange of requests and responses are required.
When the system and the use case are already covered by a maintained integration.
When you want to link an event to an action without a specific sequence of events.
When legacy logic, interfaces or systems not covered by the standard are required.
Activate messages, manage resources and receive results
The rdcom APIs provide resources for connecting business processes to the platform’s services. Availability varies by channel, function and account configuration.
-
Messaging
Send SMS, email, RCS and OTPs from the company system |
Channels, content types, individual/bulk, sender, scheduling and endpoints. -
Data and lists
Create or update the resources made available by the platform.|
Contacts, lists, profiles, consents, accounts, users and permissions. -
Automations
Link external events to available automations. |
Creation, launch, entry, pause and statistics for Journeys/automations.
-
Landing pages and lead generation
Manage the resources displayed on forms and landing pages. |
Actual operations and integration with Subscription Flows. -
Results and statistics
Retrieve technical statuses and available metrics. |
Delivery, errors, opens, clicks, campaigns, granularity and timings. -
Webhook
Receive notifications when a supported event occurs. |
Event catalogue, payload, signature, retry, ordering and latency.
From the event in the system to the outcome of the communication
Event
Whether it’s a CRM, an e-commerce platform or an application, it records an action or a change.
Request
The system sends the relevant data to the API or activates the connector.
Processing
rdcom approves the request and activates the relevant service or resource.
Communication
The message is processed on the configured channel.
Result
Status or interaction become available depending on the function used.
Return
Webhooks or API calls update the system and can trigger the next step.
Start with a supplement that’s already available if it covers your needs
The inTouch by rdcom app for linking external triggers to SMS/email sending.
HubSpot, ActiveCampaign, Typeform, Calendly, Slack, WooCommerce and other apps can be added to the Zap.
Sending SMS and RCS messages within the platform’s automations, using the data available in the project.
Integrate communications at the moments that matter
E-commerce and retail
Order, availability or shopping basket → confirmation, update or retrieval.
Services and operations
Expiry, change or anomaly → notification and service update.
CRM and sales
New lead, change of stage or appointment → welcome, follow-up or reminder.
Access and verification
Login or sensitive transaction → OTP and its result.
Customer care
Request, status or response → system update and subsequent communication.
Marketing operations
Data or behaviour → update to the resource or input into a compatible automation process.
Define the integration before writing the code
- Please specify the event, the required details, the channel and the expected outcome.
- Choose from APIs, connectors, Zapier and bespoke development.
- Check the authentication, resources, limits, errors and available environments.
- Develop and test the workflow using data and controlled cases.
- Put it into production, monitor the results and manage any exceptions.
Authentication, errors and events are all part of the project
| Area | Information to provide |
|---|---|
| Access | Base URL, HTTPS, tokens, permissions, and credential rotation. |
| Requests | Format, required fields, validation rules, and supported dimensions. |
| Responses | HTTP status codes, application errors, identifiers, and statuses. |
| Volumes | Rate limits, traffic peaks, queues, bulk requests, and capacity constraints. |
| Reliability | Retries, idempotency, duplicate handling, timeouts, and error handling. |
| Webhooks | Events, signatures, retries, event ordering, latency, and handling of missed deliveries. |
| Testing and support | Available testing environment, test data, escalation procedures, and responsibilities. |
When the standard isn’t enough, the project continues
If the system is proprietary, legacy or requires functionality not covered by the available integrations, the rdcom team can consider a bespoke development solution. The analysis, scope, responsibilities, maintenance and timelines are defined on a project-by-project basis.
APIs, messaging and support within the same ecosystem
A messaging platform and services that can be integrated with business systems.
Public technical documentation and support with project assessment.
Available connectors and the option for bespoke solutions.
Expertise in the sending, outcomes, routing and management of promotional and transactional communications.
Frequently asked questions
What are rdcom APIs?
These are interfaces that enable CRM systems, e-commerce platforms, business management systems and applications to utilise the resources made available by the rdcom platform. Endpoints, parameters and responses are described in the technical documentation.
What is the difference between an API and a webhook?
The API enables your system to request an action or retrieve a resource. The webhook sends a notification to your system when one of the supported events occurs.
What is the difference between promotional and transactional text messages?
The former relate to commercial or relationship-building initiatives; the latter are linked to an event or a transaction. The purpose, legal basis, content and management of consent must be assessed separately.
Can I integrate SMS, email, RCS and OTP into my software?
rdcom provides APIs for the supported services and functions. Channels, content, transmission methods and results must be checked against the documentation and the configuration specified for the project.
Can I connect inTouch to my CRM or e-commerce platform?
Yes, via an API, webhook or an available connector. The method depends on the system, the data to be exchanged, the events and the level of control required.
Which add-ons are already available?
rdcom has released an integration for Salesforce Marketing Cloud and an inTouch by rdcom app on Zapier. The actual scope and requirements of each integration should be checked in the relevant information sheets.
What can I do with Zapier?
The published rdcom guide describes how to link your inTouch account and how to use the ‘Send SMS/Email’ function.
Do you need a development team?
API integration usually requires technical intervention. A connector or Zapier can reduce the amount of development work required when the use case is already covered; for specific requirements, bespoke development may be considered.
How are requests authenticated?
The rdcom documentation specifies REST access via HTTPS and token-based authentication. Management, permissions and credential rotation must be defined in accordance with the project.
How long does an integration take?
It depends on the system, resources, channels, logic, testing and security requirements. A reliable estimate is determined once the event, data, action and expected outcome have been mapped out.
Where can I find the technical documentation?
The public documentation can be found at docs.rdcom.com and describes the available resources. The rdcom team can help you identify the most suitable approach for your use case.
What is the difference between using inTouch and using the APIs?
inTouch provides an environment for managing data, content, campaigns and customer journeys. The APIs enable you to keep the process within your company’s system whilst utilising the functions made available by the platform.
Is it possible to receive status updates and results in your system?
Yes, for the statuses and events supported by the function being used. The mode, payload and timing must be checked in the API and webhook documentation.
