Verimor integration | Zervanor
← All connectors

Verimor

Also an agent tool
communication

Verimor Telekom Turkish SMS integration — REST v2 outbound SMS (single and bulk), delivery reports and status, inbound messages, balance and sender headers, blacklist (opt-out) management, and İYS commercial-consent operations, with polling triggers for inbound SMS and delivery reports.

14 actions · 4 triggers

The Verimor integration lets you connect Verimor to your automations with 14 actions and 4 triggers — and every action is also a tool an AI agent can call. Examples: Send SMS, Send Bulk SMS, Cancel Scheduled Campaign, Get Delivery Status by Campaign ID, Get Delivery Status by Custom ID. No blank-canvas wiring — connect it and use it in your workflows.

Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.

Triggers 4

Events in Verimor that can start a workflow.

webhook

New Inbound SMS

Fires when a new inbound SMS arrives at your Verimor number (polling list_inbound_messages).

webhook

SMS Delivery Report

Fires when the delivery status of a sent SMS changes (polling get_status_by_id). Scope the poll to a campaign id from a prior send.

polling

SMS delivery report updated

Fires when the delivery status of sent SMS reaches a terminal state.

polling

Incoming SMS received

Fires when a new inbound SMS arrives at your Verimor number.

Actions 14

What Zervanor can do in Verimor.

GET

Send SMS

Send one message text to one or many recipients (GET /v2/send). Use for transactional notifications (OTP, order shipped, appointment reminder) and simple one-message broadcasts. Returns the campaign id as plain text on success.

POST

Send Bulk SMS

Send different messages to different recipients in one call (POST /v2/send.json). Returns the campaign id as plain text. NOTE: credentials are sent in the JSON body for this POST endpoint (verimor-01).

POST

Cancel Scheduled Campaign

Cancel a previously scheduled (not-yet-sent) campaign by its campaign id (POST /v2/cancel/{id}). Does not recall an already-sent message. Credentials are sent in the JSON body (verimor-01).

GET

Get Delivery Status by Campaign ID

Query delivery status for a campaign by its Verimor-issued campaign id (GET /v2/status). Returns a JSON array of message objects. Rate-limited to ~20 queries/minute (verimor-06).

GET

Get Delivery Status by Custom ID

Query delivery status for a campaign by your own custom_id set at send time (GET /v2/status). Returns a JSON array of message objects.

GET

List Inbound Messages

Retrieve SMS received by your number — replies and inbound keyword messages (GET /v2/inbound_messages). Returns a JSON array. Pull model — used for the new_inbound_sms polling trigger.

GET

Get Account Balance

Query remaining SMS credit / balance (GET /v2/balance). Safe, read-only — used as the connectivity test target. Returns a numeric balance as plain text (verimor-02).

GET

List Sender Headers

List the account's approved sender names / originators (GET /v2/headers). Returns a JSON array of header strings.

GET

List Blacklist

Retrieve blacklisted (opted-out) numbers (GET /v2/blacklists). Returns { total, records[] } where each record has phone, created_at, source. Max 100 records per query.

POST

Add to Blacklist

Add numbers to the blacklist (POST /v2/blacklists). Returns 'OK' as plain text on success (verimor-02). Credentials are sent in the JSON body (verimor-01).

DELETE

Remove from Blacklist

Remove numbers from the blacklist (DELETE /v2/blacklists/{phone_numbers}). Returns 'OK' as plain text on success (verimor-02).

POST

Submit İYS Consents

Submit recipient consent records to İYS for commercial messaging (POST /v2/iys_consents.json). Returns a campaign id. Credentials are sent in the JSON body (verimor-01).

GET

List İYS Campaigns

List İYS consent-upload campaigns (GET /v2/iys/campaigns). Returns { total, records[] } with id, header_name, iys_code, created_at.

GET

Get İYS Campaign Consents

Retrieve the consent records and their processing status for one İYS campaign (GET /v2/iys/campaigns/{id}/consents). Returns { total, source_addr, status, records[] }.

Automations using Verimor

Build your own automation with Verimor in the visual builder.

Frequently asked questions

What can I automate with Verimor?

14 actions are available — for example: Send SMS, Send Bulk SMS, Cancel Scheduled Campaign, Get Delivery Status by Campaign ID, Get Delivery Status by Custom ID, and more.

Which Verimor events can start a workflow?

4 triggers — for example: New Inbound SMS, SMS Delivery Report, SMS delivery report updated, Incoming SMS received.

Can Verimor be used as an AI agent tool?

Yes. Every Verimor action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.

How is the Verimor integration modelled?

Verimor is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.