Automations, API Keys & Webhooks

The current InfiniReach automation surface lives under Automations — with separate tabs for Workflows, API Keys, and Webhooks.

Important: this area moved

API keys and outbound webhooks are no longer managed under Integrations. In the current UI, go to Automations, then use the API Keys or Webhooks tab. Integrations is now for CRM-related setup such as GoHighLevel.

What lives under Automations

Workflows

Native trigger → conditions → action-step automations. Create them on /automationsand edit them in the Builder on /automations/[id].

API Keys

Credentials for programmatic access to the InfiniReach API. Send them in theX-API-Key header.

Webhooks

Outbound event delivery from InfiniReach to your HTTPS endpoint. This is separate from the Inbound Webhook workflow trigger.

Current UI screenshots

These screenshots were captured from the current PR-175 preview environment so this page matches the real product UI.

InfiniReach Automations page showing Workflows, API Keys, and Webhooks tabs
Automations overview: tabs for Workflows, API Keys, and Webhooks.
InfiniReach automation builder showing Trigger, Conditions, Action Steps, and Run History
Workflow detail page: a structured Builder, not a canvas editor.

How to use Automations

1. Create a workflow

  1. Open Automations from the sidebar.
  2. Stay on the Workflows tab.
  3. Click + New Automation.
  4. Enter a name, choose a trigger, and create the draft workflow.
  5. Click the workflow title to open the Builder page.

2. Configure the Builder

The Builder is organized into three sections, plus a run log:

Trigger

Choose what starts the workflow.

Conditions

Optional rules to decide whether the workflow should continue.

Action Steps

What InfiniReach should do when the trigger and conditions match.

Run History

Inspect payloads, condition results, step output, errors, and duration.

3. Supported workflow triggers

message.inboundmessage.deliveredmessage.failedwhatsapp.message.inboundcall.misseddevice.offlinewebhook.inbound

For non-webhook triggers, the UI includes a Test panel with editable sample payload fields and copyable {{trigger.field}} variables.

4. Supported action steps

Send SMSHTTP RequestDelay / Schedule

Outbound Webhooks vs Inbound Webhook

Outbound Webhooks

InfiniReach sends event notifications to your URL. Configure these under Automations → Webhooks.

message.inboundmessage.deliveredmessage.failedwhatsapp.message.inbounddevice.offline

Inbound Webhook

This is a workflow trigger with type webhook.inbound. It gives the workflow a dedicated receiver URL at /hook/{webhookSlug}so your external tool can start the workflow.

Create an API key

  1. Open Automations.
  2. Click the API Keys tab.
  3. Click + Create API Key.
  4. Name the key for the integration using it, such as n8n staging or Make.com prod.
  5. Copy the key immediately — it is shown once.
  6. Use it in the X-API-Key header.
curl -X POST https://api.infinireach.io/api/v1/messages   -H "Content-Type: application/json"   -H "X-API-Key: YOUR_API_KEY"   -d '{
    "channel": "sms",
    "to": "+61400000000",
    "message": "Hello from InfiniReach"
  }'

Create an outbound webhook

  1. Open Automations → Webhooks.
  2. Click + Create Webhook.
  3. Enter your HTTPS endpoint URL.
  4. Select the events you want InfiniReach to send.
  5. Optionally filter by phone/SIM/device or WhatsApp instance.
  6. Save, then use Test and the active toggle to validate delivery.

Use your app's public HTTPS webhook URL here — the URL that should receive event notifications from InfiniReach. This section only covers the dashboard setup inside InfiniReach, not the server code for your own app.

Use the Inbound Webhook trigger

  1. Create or open a workflow.
  2. In the Builder, set the trigger to Inbound Webhook.
  3. Save the workflow so InfiniReach can generate its receiver URL.
  4. Copy the /hook/{webhookSlug} URL.
  5. Choose authentication: No Auth, Header Secret, or Basic Auth.
  6. Use Start Listening to capture a test payload from your external tool.
  7. Use top-level JSON keys in conditions and {{trigger.keyName}} in steps.

Example: if your POST body is {"orderId":"123","status":"paid"}, you can check orderId or statusin workflow conditions and use {{trigger.orderId}} in action steps.

Best practices

Use separate API keys per tool. That makes revocation and auditing easier.

Rotate secrets after demos or screen recordings. Treat recorded credentials as exposed.

Return HTTP 200 quickly from webhook endpoints. Do heavy processing asynchronously.

Prefer webhook auth in production. Header Secret or Basic Auth is safer than No Auth.

Use Run History when debugging. It shows the trigger payload, condition result, step output, errors, and duration.

Need the API reference too?

Use the API reference for request formats, then come back here for the operational workflow inside the dashboard.

Open API docsIntegration docs