SMS Alert
MessagingConnect AI agents to SMS Alert, an Indian bulk and transactional SMS gateway by Cozy Vision. Agents send and schedule SMS, run OTP verification, manage contacts, groups, and templates, and pull delivery reports so transactional messaging in India stays traceable.
What This Integration Enables
SMS Alert is an Indian gateway operated by Cozy Vision Technologies in Noida, and the reason it exists as its own connector rather than as a generic SMS endpoint is that Indian transactional messaging carries obligations that most gateways do not model. A sender ID here is not a free text field. It is a header registered on the operator's DLT portal and approved on the account before it can be used, and List Sender IDs reports that approval flag. Credit is not a single balance either. Get Balance returns credits broken down per route, because the route a message travels on is a category with its own rules, not a speed setting.
What the connector gives an agent is the whole operating surface around that: sending one body to many numbers, scheduling for a future time, sending to stored groups, sending several different bodies with their own recipients in one request, running one-time password issue and validation, managing contacts, groups and templates, shortening links so a message stays inside one segment, and reading the campaign log and delivery reports afterward. Send Bulk SMS is the one worth knowing about, because it expresses something Send SMS cannot: several distinct message bodies, each with its own recipient list and its own sender ID, dispatched in a single call. That is what an agent needs when it is notifying a hundred customers about a hundred different orders.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order Notifications That Match Their Registered Template
An order ships in WooCommerce. The agent reads List Templates, finds the stored notification body, fills the order reference and courier into it, and calls Send SMS. The response carries a batch ID plus a per-recipient breakdown of message IDs and initial statuses, which the agent writes onto the order. An hour later a second flow calls Get Delivery Report with that batch ID and records the per-message state, so the merchant can answer "was the customer told" without opening the gateway dashboard. Because the body came from a stored template rather than being assembled freehand, what went out matches what was registered.
Verification Where Both Answers Look Like Success
A signup flow calls Send OTP against a template containing the code placeholder, with its own length and validity settings. When the user enters a code, the agent calls Validate OTP. This is the detail that catches naive integrations: the gateway reports a match and a mismatch as the same successful call and distinguishes them only in the message text. The connector surfaces that distinction, so the flow branches on the actual verdict rather than on whether the HTTP call worked. After three failures the agent stops retrying and opens a verification task in HubSpot with the number attached.
A Reminder Campaign That Can Still Be Called Back
A tutoring business schedules fee reminders for the first of the month. The agent builds the group with Import Contacts, then queues the send with Send SMS To Groups on a schedule and records the batch ID. If the finance team reconciles a payment before the reminder fires, the flow calls Cancel Schedule for that batch, which stops it and refunds the credits reserved for it. If the date needs to move, Update Schedule shifts it without rebuilding the audience. The whole campaign stays reversible right up until the moment it dispatches, which is not true of an immediate send.
Human-in-Loop Highlight
There is one thing this API deliberately cannot do, and that absence is where the gate belongs. Create Template stores a message name and body on the account, but the DLT-approved template ID that Indian operators require is mapped to that template separately, inside the SMS Alert dashboard, not through the API. So an agent can compose a body, store it as a template, pick a route from the ones Get Balance reports, and dispatch it, without ever having established that the wording matches what the registered header and template were approved to carry. For a transactional notification derived from a stored, already-mapped template, that is fine. For anything promotional, or anything where the agent generated new wording, it is not. So the agent stops before the first bulk dispatch of any new body and posts the evidence to the messaging owner: "New body ready for 8,400 contacts across 3 groups. Sender ID: TUTRHQ, approved on the account. Route: nondnd, 12,000 credits remaining. This body was composed by the flow and has no stored template behind it, so no DLT template mapping exists for it. Confirm the header and route are approved for this wording, or point me at a stored template and I will use that instead." The human-in-the-loop step is not proofreading. It is a compliance owner confirming that the message and the registration match, which is the one check the API cannot perform on its own.
Agent Capabilities
32 actionsMessaging
4- Send SMS Sends one message body to one or more mobile numbers in a single request. Numbers may be given with or without the country code, and the response returns a batch ID plus a per-recipient breakdown of message IDs and initial statuses.
- Schedule SMS Queues the same dispatch for a future date and time in the gateway's documented format, interpreted in the account's own time zone. Scheduling keeps a send cancellable, which an immediate dispatch is not.
- Send SMS To Groups Sends to every contact in one or more stored groups, immediately or on a schedule, on a chosen route. Groups may be addressed by numeric IDs or by a single group name, since the vendor documents both forms.
- Send Bulk SMS Sends several different message bodies in one request, each with its own recipient list and its own sender ID per recipient. This is the operation for per-customer notifications at volume, which a single shared body cannot express.
One-Time Passwords
2- Send OTP Generates a one-time password and sends it using a template containing the code placeholder, with optional length, retry and validity settings.
- Validate OTP Checks a code entered by the user against the one issued for that number. The gateway reports both a match and a mismatch as a successful call and distinguishes them in the message body, so flows must branch on the verdict rather than on the call succeeding.
Scheduling
2- Update Schedule Moves a queued batch to a new date and time, addressed by the batch ID returned when it was queued.
- Cancel Schedule Stops a queued batch that has not been sent and refunds the credits reserved for it. This is the undo that only exists while a send is still in the future.
Reports
2- Get Delivery Report Reads the per-message delivery report for a batch ID, giving the destination, sender ID, message text, message ID and delivery status, optionally filtered by sender ID or message text.
- List Campaign Log Pages through the account's sent-SMS log with campaign ID, sender ID, body, campaign name, submitting source and IP, route, message count, and credits charged and refunded. This is the audit record of what the account has actually sent.
Contacts
5- List Contacts Pages through the contacts of one group with their contact IDs, names, numbers and stored custom field data.
- Create Contact Adds a single contact to an existing group. This route identifies the group by name rather than by numeric ID, unlike the other contact operations.
- Import Contacts Imports a batch of contacts into one group in a single request, each with optional custom field values. The whole batch travels in one call, so it does not slow down as the list grows.
- Update Contact Updates the name and mobile number of a stored contact by its numeric ID. Both fields are sent on every call, so supply the current value for whichever is not changing.
- Delete Contact Deletes a stored contact by its numeric ID.
Groups
4- List Groups Lists the account's contact groups with their IDs, names, creation dates, member counts, stored settings and custom field definitions.
- Create Group Creates a contact group. Letters, numbers, hyphens and underscores are accepted in the name, and spaces are rejected.
- Update Group Renames an existing group by its numeric ID, under the same naming restrictions.
- Delete Group Deletes a contact group by its numeric ID.
Templates
4- List Templates Lists the message templates stored on the account with their IDs, titles, body text and creation dates. Reading this before a send is how a flow stays on wording that has already been reviewed.
- Create Template Stores a new message template under a given name. The API accepts the name and body only, because the DLT-approved template ID Indian operators require is mapped to the template separately in the SMS Alert dashboard.
- Update Template Updates the name and body of an existing template by ID. Both fields are sent on every call, so supply the current value for whichever is not changing.
- Delete Template Deletes a stored template by its numeric ID.
Short Links
2- Create Short URL Shortens a URL through SMS Alert's own shortener and returns the short link with its alias, click count and record ID. Used to keep a message inside a single billable segment.
- Delete Short URL Deletes a short link by the record ID returned when it was created.
Account
7- Get Profile Returns the account profile for the configured key, including username, contact details, parent account, expiry date, allowed country prefixes and the verification and KYC flags.
- Get Balance Returns remaining credits broken down per route, with each route key, its display name and its balance. This is the preflight check that stops a batch from stalling halfway.
- List Sender IDs Lists the sender IDs registered on the account with their approval flag, open flag and the date each was added. In India a sender ID must be registered as a header on the operator's DLT portal and approved on the account before it can be used.
- Update Profile Updates the profile of the account the key belongs to. Any combination of name, mobile number, email and push notification ID may be supplied.
- Change Password Changes the SMS Alert dashboard password for the account. This affects the login password only and leaves the API key unchanged.
- Register Account Creates a brand new SMS Alert account through the vendor's self-serve signup route. It does not use the configured key and does not act on the connected account.
- Request Password Reset Sends a password reset link to the email address of an account identified by username or registered email. It does not use the configured key.
Frequently Asked Questions
What can FlowRunner do with SMS Alert?
FlowRunner agents can run Get Profile, Get Balance, and List Sender IDs in SMS Alert, plus 29 more actions.
Does connecting SMS Alert to FlowRunner require OAuth?
No. SMS Alert connects to FlowRunner with an API key, no OAuth flow required.
Can SMS Alert trigger a FlowRunner workflow automatically?
SMS Alert doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SMS Alert
$100 in credits. No card required. Connect in minutes.