All connectors

Termii

Messaging

Send the right update through Termii at the right moment, with a person approving what reaches customers.

4 ways to write, each write switched on by you.

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Termii with Nexra

Connected, approved, proven.

The things teams do most with Termii, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Send a messagemessages.sendApproval by rule
  • Call with a spoken codevoice_calls.sendApproval by rule

Example flow

  1. Termii · Send a messagemessages.sendMaker-checker
  2. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Termii.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Termii
  • Termii's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

For developers

Technical detail

Termii: send SMS, WhatsApp templates and replies, and spoken-code calls; delivery reports and incoming messages as triggers.

Termii API docs
Destination actions
4
Data types
4

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

messages1
  • Send a messageDestinationNot retried automaticallyApproval before production

    Sends an SMS (or a voice or WhatsApp message) to one number from your sender ID.

voice calls1
  • Call with a spoken codeDestinationNot retried automaticallyApproval before production

    Calls the number and reads out a numeric code you choose (4 to 8 digits).

whatsapp messages1
  • Reply on WhatsAppDestinationNot retried automaticallyApproval before production

    Sends a free-form WhatsApp text inside the 24 hours after the customer last wrote to you.

whatsapp template messages1
  • Send a WhatsApp templateDestinationNot retried automaticallyApproval before production

    Sends an approved WhatsApp template through your Termii WhatsApp device.

Access and limits

Authentication
Termii API key
Plans and access
A Termii account with credit; each message is billed. Sender IDs and WhatsApp devices must be approved by Termii before use.
Test environment
Termii has no sandbox. Test with your live account and a small amount of credit, sending to your own number.
Rate limits
Termii answers 429 when you send too fast and publishes no fixed limit; Nexra backs off and never repeats a send.
Pagination
Termii sends return one result; reads are not offered.
Provider events
Termii posts delivery reports, incoming messages and device status to the webhook address in your account, signed with X-Termii-Signature (HMAC SHA512). Flows can start the moment something happens: when a message is delivered or fails; when a customer replies.

Before you build a flow

  • Sending is billable and approval-gated like other message sends; Termii has no idempotency key, so an uncertain send is never repeated.
  • Reads (balance, message history, sender IDs, number checks) are not offered because Termii takes the API key in the request address. Delivery reports and replies arrive through the Termii trigger.
  • Termii has no sandbox; test on your live account with your own number.
  • Bulk sends, phonebooks, campaigns and one-time PIN flows are not offered.
  • Termii does not say which key signs its webhooks; Nexra uses the Secret Key on your API token page.

Developer reference

  1. Create the Termii credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Termii, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/termii and the Connections API.