Automas
Business calling, built into your software
Give each application its own numbers, credentials, and call events — so your teams can place and receive calls from the tools they already use.
How it works
From portal to live calls
Your platform admin allocates trunks and number ranges. You configure everything else in the tenant portal — then your backend talks to Automas with a per-application API key.
- 01
Confirm capacity, then create extensions
Open Infrastructure to verify trunks and ranges. Create agent extensions, wait until they are active, and keep SIP numbers ready for your users.
- 02
Register each business system as an application
Sales CRM, Support Desk, Billing ERP — one portal application each. Assign exclusive extensions and pick the trunk that sets outbound caller ID.
- 03
Issue an API key and store it server-side
One key per application. Your PHP, Python, Go, Node, or other backend uses it to list numbers and fetch dialer credentials — never the browser.
- 04
Register a webhook and connect the dialer
Receive signed ringing / answered / ended events for that app’s numbers only. Pass SIP fields to the softphone; keep the Automas key on the server.
Tenant portal
Everything your developers need
After tenant login you manage calling for every application in one place — with isolation between systems and guidance for any backend stack.
Overview
See readiness at a glance — applications, extensions, webhooks, and what still needs finishing before you go live.
Infrastructure
Review the trunks, DIDs, and extension ranges your platform admin allocated. Capacity is visible; provisioning stays controlled.
Extensions
Create agent numbers on an assigned trunk, wait until they are active, then map each person to a SIP number — not a database id.
Applications
Register every CRM, ERP, or dialer as its own app. Assign exclusive extensions so Sales never sees Support’s numbers.
API Keys
One Bearer token per application. Copy once, store on that system’s server, and never send it to the browser or softphone.
Webhooks
One HTTPS endpoint per app for signed call events. Test delivery, rotate secrets, and verify HMAC before you act.
Team
Invite colleagues to the same tenant. Admins manage apps, keys, and extensions; members can follow the guide and docs.
Setup Guide & API Docs
First-to-last checklist plus copy-paste samples for cURL, Node.js, PHP, Python, and Go — tuned to your tenant and apps.
Built for isolation
Multi-app calling without shared secrets
Several applications under one company is normal. Automas keeps keys, webhooks, and numbers scoped so products stay independent even when they share the same PBX.
One key, one webhook per app
Rotate or revoke without touching other systems. Env prefixes stay unique per application.
Exclusive extensions
A number belongs to a single application. Credentials and call events never cross that boundary.
Stack-agnostic API
Same HTTPS JSON endpoints for Node, PHP, Python, Go, and anything else that can call a REST API.
Dialer-safe by design
Browsers and softphones receive SIP login fields only. Telephony administration stays in the portal.
Next step
Open your tenant portal
Sign in to walk the Setup Guide, create applications, issue API keys, and register webhooks. In-portal API Docs include samples for your stack. Questions? hello@automas.com.bd