Console overview

The Polymorfa Console is the browser interface for your account, teams, and projects. A team groups your projects and members. The active team and project in the URL determine which resources you are viewing.

​

Operational errors

When recorded API or webhook failures occur, a Console banner shows counts from the last 24 hours. It follows your selected team and project. Choose View errors to open Logs → Errors. The banner remains available when Analytics is disabled; billing alerts take priority. Manage log and analytics destinations in Project Settings → Drains. See drain setup and analytics export. Select Page guide to open the documentation for the page you are viewing. The sidebar’s Documentation link opens the full documentation site, and Help Center opens support answers in English and Brazilian Portuguese.

​

Support

Open Chat with us in the Console to contact support. Feedback and Report a bug open their forms inside the chat. Use the Help Center for answers to common support questions. Use the sidebar’s copy button to copy your support code and enter it manually when talking to support. Copying does not submit it. The Help Center chat form requires the code; Console chat leaves it optional. If you cannot access your code or chat, email support@polymorfa.com. Review attachments and remove credentials and unrelated customer information.

​

Phones and tablets

On screens narrower than 768 pixels, the navigation sidebar is hidden. Open it with the menu button at the top left of the page; it closes after you choose a page. Wide tables scroll horizontally. Detail panels that sit beside a table on wide screens, such as audit log event details, appear below the table.

​

Team and project context

The team switcher shows workspaces available to your account. The top-left sidebar banner shows the team’s billing mode, Free or Pay-As-You-Go. Project selectors show project names. Changing team or project changes the current resource scope; it does not grant access outside your live membership. The team overview has three columns: Usage and Billing, Projects, and Analytics/logs. Usage shows number connections and your real-number and project allowances. Project cards show connection and spending-limit progress bars, messages and last activity. Choose Gallery for cards or Table for rows, and search projects by name. On Pay-As-You-Go, owners and admins see their current credit balance, monthly bonus and next bonus milestone, today’s cost and monthly spending. Automatic top-ups show the saved balance threshold and credit amount; scheduled top-ups show their next date, amount, frequency and status. Pie charts show connections and project spending. The daily spending chart stays with Billing. Analytics shows recorded message activity, completed 24-hour read and reply rates, your response time, waiting replies and answered or missed incoming calls from the last 24 hours. Select View all to open the full Analytics page. When Analytics is off, owners and admins open its existing enable flow; collection remains opt-in. Missing measurements and incomplete rates show —, not zero. Recent logs remain available independently of Analytics. Select a project name to open Get Started. Payment statuses use the same labels as Billing. Billing and logs show unavailable states when their reads fail. Free teams see their real-number and project allowances. The billing summary shows Free, the confirmed included real-number allowance and a direct Upgrade to Pay-As-You-Go action for owners and admins. They do not request or display paid spending, balances, project budgets or daily spending charts. A Free billing mode does not produce a spending-unavailable error. Pay-As-You-Go read failures remain visible and offer Retry. After upgrading, the billing summary shows credit balances and funding details instead of the Free allowance. A selected project opens a full page with Get Started, Overview, Activity and Settings tabs. Funding appears for Pay-As-You-Go owners and admins. The project header keeps Numbers, Usage, Project settings, the project ID copy button and available API actions above the tabs. Each tab has a shareable URL. Opening a project without a tab link always selects Get Started, even after its checklist is complete. The project selector at the top switches projects. Overview shows connection coverage, message totals and Analytics. Activity shows recent logs, campaigns, template approvals and Flows. Funding shows the existing project budget; Usage keeps the limit and priority controls. Get Started contains the project checklist. Settings lets owners and admins edit the project name, icon and default number plan, and links to API keys, webhooks, Drains and QuickLink settings. Inside a project, Analytics and recent logs follow that project. Funding shows its paid budget when applicable. Activity shows recent campaign results, template approvals and Flow counts. The sidebar shows the team’s Free or Pay-As-You-Go billing mode; the default number plan is shown separately. Manage limits opens Usage, where owners and admins manage project and number limits. From Numbers, the row menu’s Budget action opens that number’s control directly. See spending budgets.

​

Resource details

The top bar shows the page or focused resource. When you open a resource, the breadcrumb shows its list and name, such as Customers / Mina. The last item is bold. Select the earlier item to return to the list. Select the resource name with the up/down chevrons to search for and open another resource in the same scope.

​

All projects

Choose All projects in the project selector to view the whole team. Type in Find project at the top of the selector to filter the list, and press Esc to close it. The current page stays open when you switch between All projects and a project. A page that shows one record or a create form returns to its list, because each record belongs to one project. These pages total every project in the team and show how each project contributes: The By project table appears when the team has more than one project. Campaigns, Customers, Flows, Templates, and Safety belong to one project. In All projects, these pages list the team’s projects instead of showing empty data. Choose a project, or type in Find project to filter the list, and the same page opens for it. If your team has one project, the page opens for that project without asking. If the URL names a project that no longer exists or that you cannot access, the page shows Project not found and the same project list. The Console, including onboarding, is available in English and Brazilian Portuguese. Choose a language under Account > Settings, from the account menu, or from the onboarding language control. See Language.

​

Returning to the Console

Opening polymorfa.com/console reopens the team and project you last worked in. If that team is no longer available to your account, the Console opens your first team instead. Your last scope is recorded in the browser you used, so a different browser or a cleared browser opens your first team. Returning to a project opens Get Started, even after its checklist is complete. Choose Overview to see project activity and connection coverage. Every Console destination keeps the team and project in the address, so a bookmarked or shared page opens in the scope it names. Settings and Logs open on their first pane: project settings open on General, team settings on General, and Logs on All. Select the back arrow in Settings, Logs, or Account to restore the main navigation while keeping the current page open. Choose another destination to leave the page. Select Settings, Logs, or your account again to reopen its navigation.

​

Analytics

Enable Analytics to view WhatsApp number activity, completed 24-hour read and reply rates, response times, call outcomes and connection problems. Use the existing date picker and number selector at the top. API error rates link to Logs → Errors. Team owners and admins control one enable/disable setting. See WhatsApp analytics for metric definitions, measurement coverage and API access. Credits and limits remain on Usage.

​

Customer workflows

Use the Console to:

• manage team members and projects;
• create team keys and project tokens;
• create, pair, inspect, and control sessions;
• configure client-token rules, webhook endpoints, and embedded signup;
• review usage, credits, payment history, and billing settings; and
• manage verified email addresses, passkeys, email OTP, TOTP, social sign-in connections, and active browser or device sessions.

Available actions depend on the team’s billing mode (Free or Pay-As-You-Go), add-ons, number tier, project stage, and features enabled for your team. The Console shows only actions available to the active team and project.

​

API boundary

The public Platform API is available under /platform/*. It accepts a team key or verified dashboard bearer and rejects project tokens. Server integrations that call Messaging API, MCP, or bridge operations must use a credential supported by that operation’s generated reference. Dashboard bearers are not customer API keys and should never be copied into an integration. Browser and mobile integrations should receive a short-lived client token limited to the actions they need.

​

Code samples for each page

Console pages that have a public API equivalent show a </> button. Buttons appear after the page confirms access and availability. Disabled Customers and QuickLink pages, unavailable pages, and the Free billing upgrade screen do not show API actions. The button sits beside the page’s main action in the table toolbar, alongside search, filters, and sorting, such as New campaign, New number, or Add endpoint. The Projects list places it beside New. Pages without a main action show it in the page content. The button opens the API for that page: the requests that do the same work from your own code, each with its method, path, required permission, and a link to its API reference. Choose Node.js, cURL, Python, Go, PHP, or Ruby. The console remembers your choice in that browser. Node.js samples use the TypeScript SDK; the other languages call the HTTP API directly. Every sample reads your key from the POLYMORFA_KEY environment variable and sends a Polymorfa-Version header. Replace values in angle brackets, such as <project-id>, before running a sample. Copy for your coding agent uses the same control as the homepage setup prompt. Both prompts follow the same structure: context, task, documentation, constraints, and verification. The API panel includes the selected page’s requests, base URL, version, and credential requirements. Each request includes its permission and a link to the Markdown version of its reference page. It also links the documentation index for agents at /llms.txt. Paste it into Claude, ChatGPT, Cursor, or another coding agent. Pages that only exist in the console, such as Analytics, Notifications, and account settings, have no </> button. Some pages show only part of their work through the API: for example, you create API keys in the console, and the API lists and deactivates them.

​

Where to go next

​

Project setup

Open a project to see its setup checklist. Progress follows current records: a connected number, an unrevoked and unexpired project key, an enabled project webhook, and an observed successful API read. API observation depends on retained request logs; a missing observation does not prove that access failed. Start onboarding by choosing your language and theme above the team fields. Use the language and theme icons at the top to change them later. The language you choose is saved on your account; see Language. Setup progress appears at the bottom center. During onboarding, choose Set up with your AI agent or Manual set-up in the Console. AI setup appears first with a purple Recommended label. It gives you a prompt to copy and an input for your agent’s answers. Manual setup asks one question at a time. Both paths reuse answers you already provided. Your answers select the features to focus on in your project. Choose who you build for, the platforms you already use, and the connection you want in Polymorfa. Existing platforms lead to questions about assets you want to reuse, such as message templates, Flows and catalogs. Business outcomes lead to relevant follow-ups about workflows, conversation history and application hosting. Select several answers wherever they apply. For example, marketing can add Templates and, when you choose Polymorfa’s workflows, Campaigns. Building a product for other businesses can add QuickLink. Hosted history enters the checklist when you choose to store conversations in Polymorfa. Keeping history in your own application leaves it out. These choices do not enable storage, connect numbers, migrate assets or grant feature access. Meta approval and Flow publication remain separate requirements. Choose Just the basics for my business to start without optional features or customer-connection tasks. Skip opens the project without saving these answers. Product context is also optional. Relevant offers appear during manual setup. Dismiss them with the close button, or swipe them sideways on mobile. In AI setup, Ask your coding agent groups the prompt and Import agent answers. Copy the prompt, ask the agent about your business, then paste its JSON answer block in that section. Finish saves the collected answers and opens your checklist, including any choices left explicitly unknown. For a partial answer block, Continue opens the relevant unanswered questions. Each manual question offers Ask your agent instead; it defers that decision and adds it to the follow-up prompt at the end. Confirmed answers are reused. The block accepts only the listed choices; keep credentials and session data out. A team owner or admin saves the shared plan. Once onboarding is complete, the project opens its setup checklist. Use Edit setup plan to change answers later. New projects start with undecided choices. If another person saves first, your editing draft stays open. During onboarding, select Reload saved answers before continuing. On the project checklist, use Review updated plan. Session Import connects Linked Devices. Choose Linked Device or both connection types in the setup plan to import existing Baileys or whatsmeow state. An Official API-only plan starts without a Linked Device session import. Selected features become numbered tasks and count toward progress. Each task includes an AI-assisted prompt and Manual instructions with action cards and reference links. Catalog and message history tasks check availability before configuration. Use Add to setup in Other features to select another feature in the plan. Unselected features remain outside the progress count. Browser and mobile choices add client-token guidance; project credentials stay on a server. SDK and HTTP choices change the references. Polymorfa Graph adds its Meta-compatible API guide. A Baileys or whatsmeow answer adds Session Import guidance; it does not start an import. Selecting only polling removes the webhook task. Selecting webhooks alongside polling keeps it. Use Copy inside a prompt panel to hand over that task and observed setup facts. Follow agent setup to install tooling. The prompt contains no credentials and asks the agent to check access before making changes. Setup tasks use Not started, In progress, and Done. Connecting a project is Done when it has a connected number and an active project key. Webhook setup is Done when an endpoint is enabled. API verification is Done when an active project key and a successful project read are present in retained activity. Opening a task or copying a prompt does not change progress. If a number disconnects, a key is revoked or expires, or a webhook is disabled, its task reflects the change after refresh. The browser remembers your setup method for each project. Use Change setup method to revisit agent setup. Done describes the task’s setup requirement; it does not confirm provider approval, feature eligibility, or message delivery.

​

Select a time range

Date-range controls use a split button. Open the calendar on the left for a custom date range; use the dropdown on the right for a recent period. Click a start and end date, jump through the month or year selectors, choose Local or UTC, and apply the range. The calendar fits within a phone viewport and disables dates outside the available range. Logs and Activity also disable days without recorded activity. See Logs and audit history.