Create a gateway
The quick-create card, field by field: pick FROM and TO, drop in a template, go live.
Last updated October 6, 2026
A gateway has two sides: a FROM (where your users' messages come in) and a TO (where Portarus delivers them, usually your agent). The quick-create card walks both. You do not fill a long form — you pick each side from a list and the card shows only the few fields that side actually needs.
TO — your destination
Start here: the destination gates everything else. Pick the platform your agent runs on — n8n, Make, Zapier, LangChain or a custom endpoint — and the card adapts to it.
| Field | Required | Details |
|---|---|---|
| URL | Yes | The HTTPS webhook your platform exposes, where filtered messages are delivered. Must be publicly reachable; internal/private IPs are blocked. |
| Secret Key | Auto | Generated for you and sent as Authorization: Bearer … on every delivery. Copy it into your destination so it can verify the request is really from Portarus. |
Under the URL field, "Where do I find this URL?" expands the per-platform steps — and for n8n, Make and LangChain those steps link to an importable template that already carries the webhook and the secret check. Import it, copy the URL it exposes, paste it back. Under the Secret Key, "copy it into your destination as shown here" expands exactly where that secret goes on your platform.
Fastest path: drop in the template for your platform. It wires the webhook, the routing on the delivery envelope, and the secret verification in one import. Browse them all under Resources → Templates.
FROM — your source
Next, pick where messages come in: WhatsApp Business, Telegram, Instagram, Messenger, Slack, Discord, or a custom webhook. For a known channel the card pre-fills a sample payload and the field mapping; for a custom webhook you paste a sample and map the two fields yourself.
| Field | Required | Details |
|---|---|---|
| Sample payload | Yes | One real (or realistic) message from your source. Values don't matter — only the shape, so the card can list the keys to map. |
| User ID | Yes | The key that identifies who sent the message. Pre-selected for known channels. |
| Message | Yes | The key that holds the message text. Pre-selected for known channels. |
See Payload mapping for how the two paths are resolved.
Advanced settings (optional)
Every filter is on with sane defaults — you can go live without touching them. Expand Advanced settings to tune unification, rate limiting, deduplication, a token cap, a blacklist, the security envelope and keyword routing. Each has its own page under Gateways.
Go live
When the destination is set and the two fields are mapped, the gateway is live. The card hands you a Gateway URL and a Secret to paste into your source channel. The secret is shown once — copy it immediately. All cryptographic keys are generated and managed for you.
Optional but recommended: send a mock payload from the card to confirm your destination receives and acknowledges a delivery before any real traffic arrives.