Odoo 19EUR 1 provider wrapper

ClickSend SMS Gateway

Activate the maintained ClickSend template inside our flagship Dynamic SMS Gateway module, configure it with your provider account, and route normal Odoo SMS through it.

Read the configuration guide

A focused add-on powered by Dynamic SMS Gateway

Important: this is not a second SMS engine and it does not include a ClickSend account. It depends on Dynamic SMS Gateway, which supplies the gateway screens, routing, request rendering and status handling.

Automatic dependency

Installing this wrapper also installs Dynamic SMS Gateway when it is available in the addons path.

Active on installation

The included data marks the ClickSend gateway active. You only need to add your credentials and sender.

No duplicate gateway

The wrapper reuses the existing Dynamic SMS Gateway provider template, so it updates the same gateway instead of creating a duplicate.

How the two modules work together

1. Install this wrapper

Odoo resolves and installs the shared Dynamic SMS Gateway engine.

2. Activate the template

The exact core XML record is updated with the current endpoint, mapping and active state.

3. Enter provider details

Replace credentials and every bracketed sender placeholder with values from your ClickSend account.

4. Select custom routing

Turn off Use IAP, choose ClickSend as Default Gateway and send from normal Odoo SMS actions.

ClickSend API profile included

Endpoint	https://rest.clicksend.com/v3/sms/send
Request	POST JSON
Authentication	ClickSend username (Username), API key (Password)
Field mapping	messages[0]: to={phone}, body={message}, source=your sender
Success handling	200; recognizes SUCCESS and message_id
Provider reference	Official ClickSend API documentation

Sender: Replace [Your Sender ID] with a sender permitted for the route.
Provider note: ClickSend may replace or restrict sender IDs for some destinations.

Installation and configuration

Place this module and the Dynamic SMS Gateway module in the Odoo 19 addons path, update the Apps list and install this wrapper.
Enable developer mode if needed, then open Settings → Technical → SMS / Phone → SMS Gateways. Remove the default Active search filter when you want to inspect every packaged template.
Open ClickSend. Replace all values starting with YOUR_ and every sender example inside square brackets.
Configure authentication: ClickSend username (Username), API key (Password).
Configure the sender: Replace [Your Sender ID] with a sender permitted for the route.
Open Settings → General Settings → SMS, turn off Use IAP, select ClickSend as Default Gateway, and choose whether IAP Fallback is allowed.
Send one controlled test to an E.164 number, using a recipient and sender allowed by your provider account.

Why Use IAP matters: if it remains enabled, Odoo may send through its IAP service instead of this custom gateway.

Routing and message status

Predictable gateway selection

Default Gateway handles messages when no specific rule wins.
Country-prefix routes and sequence can select another active gateway.
Several provider wrappers can coexist when routes are configured clearly.
IAP fallback is attempted only when enabled and available.

Status meaning

The template checks 200; recognizes SUCCESS and message_id.
The provider message identifier is stored when returned.
API acceptance is not final handset delivery.
Delivery receipts need provider callbacks and the proper inbound/status integration.

Troubleshooting checklist

No placeholder credentials or sender values remain.
Use IAP is off and ClickSend is the Default Gateway.
No country-prefix route or sequence selects another gateway.
Recipient is E.164 and sender is approved.

Account has balance, entitlement and destination permission.
Trial, registration and geographic restrictions are satisfied.
HTTP response and redacted provider error are reviewed.
One recipient works before campaign testing begins.

Security and scope

No credentials, provider account, sender number or SMS credit are included.
Restrict gateway settings to trusted administrators and never place secrets in XML, screenshots or support messages.
Provider charges, sender registration, recipient consent, opt-out and regulatory compliance remain the buyer’s responsibility.
This wrapper is for outbound transport. Add Two-Way SMS & CRM Inbox for webhooks, replies and two-way routing.

Other Corvus modules on Odoo Apps

Build a complete SMS/MMS workflow

Start with this provider wrapper and Dynamic SMS Gateway, then add only the operational features your team needs.

SMS & MMS Messaging Suite

Complete SMS/MMS suite with gateway transport, inbound routing, workspace, chatter tools and floating conversations.

View on Odoo Apps

Dynamic Two-Way SMS Routing

Provider webhooks, multiple business numbers, CRM/contact reply routing, validation and inbox fallback.

View on Odoo Apps

SMS Inbox & Composer

Operator composer and conversation workspace for daily messaging.

View on Odoo Apps

SMS Chatter Conversations

Business-number SMS/MMS tabs inside Odoo chatter.

View on Odoo Apps

Floating SMS Chat

Floating customer conversations while users continue working.

View on Odoo Apps

Corvus SMS Translation

Language preferences and multilingual messaging helpers.

View on Odoo Apps

Corvus SMS Loop Lookup

Phone lookup and enrichment for inbox operations.

View on Odoo Apps

Bulk SMS Marketing

Campaign templates, reply matching and CRM follow-up.

View on Odoo Apps

Frequently asked questions

Does it work without Dynamic SMS Gateway?

No. The core module supplies the engine and this wrapper supplies one active provider profile.

Is the gateway active immediately?

Yes, but live credentials and sender details are still required.

Can I use several providers?

Yes. Configure the default, sequence and country-prefix rules so selection is deterministic.

Does it receive replies?

No. Install Two-Way SMS & CRM Inbox for provider webhooks and reply routing.

More provider gateways

Choose another SMS provider

Use the same flagship Dynamic SMS Gateway engine with these focused EUR 1 provider wrappers. This carousel contains gateway wrappers only, without repeating the SMS feature modules shown above.

Bandwidth

Focused Bandwidth provider template for the Dynamic SMS Gateway module.

View Bandwidth Gateway

ClickSendCurrent

Focused ClickSend provider template for the Dynamic SMS Gateway module.

View ClickSend Gateway

CM.com

Focused CM.com provider template for the Dynamic SMS Gateway module.

View CM.com Gateway

LoopMessage

Focused LoopMessage provider template for the Dynamic SMS Gateway module.

View LoopMessage Gateway

MessageBird

Focused MessageBird provider template for the Dynamic SMS Gateway module.

View MessageBird Gateway

Nexmo (Vonage)

Focused Nexmo (Vonage) provider template for the Dynamic SMS Gateway module.

View Nexmo (Vonage) Gateway

Plivo

Focused Plivo provider template for the Dynamic SMS Gateway module.

View Plivo Gateway

Telnyx

Focused Telnyx provider template for the Dynamic SMS Gateway module.

View Telnyx Gateway

Twilio

Focused Twilio provider template for the Dynamic SMS Gateway module.

View Twilio Gateway

Vonage

Focused Vonage provider template for the Dynamic SMS Gateway module.

View Vonage Gateway

Previous gatewaysNext gateways

Support policy

60-day bug-fixing support

What is covered

We provide bug-fixing support for 60 calendar days from the Odoo App Store purchase date for reproducible defects in the unmodified module running on its supported Odoo 19 version.

Report the module version, Odoo version, reproduction steps, expected result, actual result, HTTP status and a redacted provider response to support@corvusnexus.com.

What is not covered

Free support does not include installation services, server administration, provider-account setup, sender approval, training, customization, feature requests, migrations, third-party conflicts, provider API changes, provider outages or issues caused by modified code or incorrect configuration.

Work outside the included scope may require a separate paid support or customization agreement.

No warranty and production responsibility

The software is supplied “AS IS” and “AS AVAILABLE,” without warranty. Always test the module, provider credentials, routing, sender identity, delivery status and failure behavior in a dedicated staging or sandbox database before deploying it to production. Keep verified database and filestore backups and prepare a rollback plan.

You are responsible for production deployment, configuration, provider charges, message content, recipient consent, regulatory compliance and operational monitoring. To the maximum extent permitted by law, Corvus Nexus Technologies LTD is not responsible for data loss, downtime, misconfiguration, provider failure, unexpected messaging charges, or failed, delayed, duplicated or misrouted messages. See the packaged LICENSE file for the complete license and liability terms.

Support and demonstrations

Send your Odoo/module version, HTTP code and a redacted response. Never send API secrets.

Email supportCorvus NexusGateway engine demo

Odoo is a trademark of Odoo S.A. ClickSend is a trademark of its owner. This independent integration is not endorsed by the provider.