Connect LINK Mobility with Inxmail

Use LINK Mobility to extend your Inxmail workflows with additional communication channels. SMS, RCS, and WhatsApp messages can be triggered via webhooks to LINK Mobility API endpoints, for example for reminders after an email has been sent. This lets you use existing Inxmail processes efficiently for cross-channel marketing communication.

  • More channels from Inxmail workflows: Trigger SMS, RCS, and WhatsApp messages via LINK Mobility directly from existing workflows.
  • Less system overhead: Use native Inxmail capabilities instead of setting up an additional sending system for LINK Mobility.
  • Efficient follow-ups: Extend email journeys with scheduled messages, for example as SMS reminders after invoice emails have been sent.

Request a demo Discuss the integration

Less manual effort

Messages via LINK Mobility are triggered from Inxmail workflows without building a new sending system for them.

Relevant contact moments

Add SMS, RCS, or WhatsApp to your email communication and reach contacts through suitable additional channels.

Fast triggering via webhook

Inxmail webhooks address LINK Mobility API endpoints and connect workflows with message delivery.

How the integration works

The connection uses the Inxmail workflow feature Webhooks. Within a workflow, a defined trigger is used to address LINK Mobility API endpoints. LINK Mobility then handles the delivery of commercial messages via SMS, RCS, or WhatsApp.

  • Workflow in Inxmail: Existing Inxmail workflows define the trigger for message delivery.
  • Webhook trigger: The workflow calls LINK Mobility API endpoints via webhook.
  • Delivery via LINK Mobility: LINK Mobility sends the triggered messages via SMS, RCS, or WhatsApp.
  • Existing platforms: Access to both Inxmail and LINK Mobility is required for the connection.

Use cases for LINK Mobility with Inxmail

LINK Mobility is suitable for marketing and customer communication when email journeys in Inxmail need to be extended with additional mobile communication channels.

  • SMS reminders after email delivery: Trigger an SMS via LINK Mobility when a reminder is needed X days after an invoice email has been sent.
  • Marketing communication via mobile channels: Use SMS, RCS, and WhatsApp as additional channels for commercial messages within your Inxmail workflows.
  • Extend existing Inxmail processes: Existing customers trigger message delivery via LINK Mobility using native Inxmail capabilities without setting up an additional sending system.
Inxmail security: Logos of certifications and memberships

Security and data protection

The connection has a clear separation of responsibilities: Inxmail triggers message delivery via webhooks, while LINK Mobility handles delivery through the respective communication channels. This is a connection built with native Inxmail capabilities, not a static integration.

  • Existing platform access: Access to both Inxmail and LINK Mobility is required.
  • Webhook-based triggering: The connection uses the Inxmail workflow feature Webhooks to address LINK Mobility API endpoints.
  • Clear system separation: Inxmail triggers the delivery; LINK Mobility handles delivery via SMS, RCS, or WhatsApp.
FAQ

Frequently asked questions about LINK Mobility with Inxmail

We answer the most common questions here. If you would like to know more, our team is here for you.

Which channels does LINK Mobility support?

LINK Mobility is a gateway provider for sending commercial messages via SMS, RCS, and WhatsApp. These channels can be triggered within Inxmail workflows via webhooks.

How does it work with Inxmail?

Inxmail uses the workflow feature Webhooks to address LINK Mobility API endpoints. This triggers message delivery via LINK Mobility directly from an Inxmail workflow.

Which use cases is the connection suitable for?

The connection is suitable for commercial messages via SMS, RCS, and WhatsApp. One concrete example is an SMS reminder X days after an invoice email has been sent.

What are the prerequisites?

Access to both platforms is required. As soon as a test or production version of LINK Mobility is available, the Inxmail Connected Solutions team can support the setup within Inxmail on request.

Is this a static integration?

No. The connection to LINK Mobility is not a classic static integration. It is implemented with native Inxmail capabilities via the workflow feature Webhooks.

Start mobile follow-ups from Inxmail workflows

Connect your Inxmail workflows with LINK Mobility and trigger SMS, RCS, or WhatsApp messages directly from existing processes. This extends your email communication with additional mobile channels and helps you implement reminders or marketing messages more efficiently.

  • Get started faster: Use existing Inxmail workflows and existing platform access for the connection.
  • Expand channels deliberately: Add SMS, RCS, and WhatsApp to email communication via LINK Mobility.
  • Deliver campaigns more efficiently: Trigger messages automatically via webhook instead of setting up separate sending systems.

Request a demo Discuss the integration