Netgsm in the Zervanor Engine: SMS, OTP and Delivery Reports

Netgsm is the last mile of most Turkish automations — the text that tells a customer their invoice is ready, the OTP that verifies a login, the reminder that a payment is due. It’s rarely the whole job, but almost every flow ends with it.

Zervanor is the automation engine behind vertical SaaS products, and Netgsm is modelled in it as a versioned connector pack — so that final message is a step in a workflow rather than a manual send. Here is what the engine covers.

What the Netgsm connector does

The Netgsm connector covers the real messaging surface — verified against Netgsm’s official REST v2, 8 actions and polling triggers:

• Outbound: Send SMS, Send OTP SMS, Cancel Scheduled SMS.
• Insight & account: Get Delivery Report, Get SMS Statistics, List Sender Headers, Get Account Balance.
• Inbound: Get Incoming SMS.
• Triggers that start a flow: Incoming SMS Received and SMS Delivery Report Updated — polled, so an inbound message or a delivery status can kick off automation.

It’s agent-ready, so an AI agent can draft the message, pick the right sender header, and send — or read an inbound reply and decide what to do next.

4 messaging automations worth building

1. Order / invoice → customer SMS. The delivery leg of every commerce chain — when an order ships or an e-Fatura is cut, text the customer the tracking or invoice link automatically.

2. Login / checkout → OTP verification. Use Send OTP SMS to verify a phone number as part of a signup or payment flow, without a separate verification vendor.

3. Overdue invoice → SMS reminder. When an invoice ages past due, send a polite reminder on a schedule — collections without the manual chase.

4. New employee → welcome SMS. When HR onboards someone, send the welcome-and-first-steps text automatically as part of the onboarding flow.

What the engine already runs

These are not hypotheticals — each is modelled with Netgsm as the delivery step:

• Trendyol Order → Paraşüt e-Fatura → Netgsm SMS — the flagship commerce chain, SMS as the last mile.
• Kolay İK New Employee → AI Onboarding → Netgsm Welcome SMS — HR onboarding with an AI step, texted.
• Paraşüt Overdue Invoice → Netgsm SMS Reminder — automation #3 above.
• Trendyol Return → Paraşüt Return Invoice → Netgsm — returns closed with a customer text.

Want a two-way flow — an Incoming SMS Received that an AI reads and routes? That one is not modelled as a template yet, and we will not pretend it is. Describe it in plain language and Zervanor assembles it from your real connectors, showing every step before it runs. Prefer a different gateway? Verimor and Turkcell e-Şirket are ready alternatives.

Why teams pick Zervanor

The whole chain runs as a single workflow execution, and the agents that handle the reading, judging and drafting run in the same runtime as the workflow itself.

See the full Netgsm connector reference for all 8 actions, or start with a template above.

FAQ

Can it send OTP codes? Yes — Send OTP SMS is a real action against Netgsm’s official API, usable as a step inside a signup or checkout flow.

Can I use my own sender header? Yes — List Sender Headers surfaces your approved headers so a flow can pick the right one.

How does Zervanor connect to Netgsm? Through Netgsm’s official REST API with credentials you connect once; delivery reports and inbound messages arrive over polling triggers.