Integrations
Integrations represent external applications linked to Pingo Notify, authorized to access resources such as connections, plans, and messaging.
What are integrations?
An integration is the link between Pingo Notify and an external application, such as a plugin, system, or platform.
An integration is not a WhatsApp session.
It is the authorization that allows an application to access Pingo Notify.
Through an integration, an application can securely and controllably interact with the messaging system.
What are integrations used for?
Integrations allow external applications to:
- Send messages
- Access available connections
- Query plan information
- Use messaging resources
- Operate within the granted permissions
Without an active integration, the application cannot access Pingo Notify.
What does this screen show?
The Integrations screen displays all applications already linked to your Pingo Notify account.
Each item in the list represents:
- An integrated application (e.g., WordPress)
- An active authorization
- A valid link to the messaging system
Example: WordPress integration
When you integrate the WordPress plugin with Pingo Notify:
- WordPress becomes an integration
- The WordPress account gains access to the messaging system
- The plugin can:
- List connections
- Use active connections
- Query plan information
- Send messages based on site events
The integration grants access.
The connection defines which WhatsApp will be used.
Integration vs Connection
- Integration: link with the application (e.g., WordPress)
- Connection: WhatsApp session (QR Code scanned)
An integration can use one or more connections, depending on the configuration.
AI integrations (OpenAI and Anthropic)
There are two directions of integration, and they are opposites:
- App → Pingo (e.g. WordPress): the authorization for an external system to use Pingo Notify.
- Pingo → provider (e.g. OpenAI, Anthropic): the credential Pingo uses to call an external service on your behalf.
AI integrations are the second kind, and they are available on any plan.
What they store
Only the API key. Nothing else.
There is no "default model" on the integration. The model is chosen by whoever uses it, and choosing is mandatory — so swapping a credential never changes the behaviour of an agent nobody edited.
The key is write-only: it is never returned by the API. When editing, leaving the field blank keeps the stored key — that is how you rotate a token without reinstalling.
Who uses the credential
Two helpdesk features, independent of each other:
- AI agents — reply to customers on their own. Each agent picks its own integration and model.
- Composer assistant — the AI button in the agent's reply box (suggest, rewrite, fix, summarize). It has its own configuration.
Deactivating or removing the integration silences every agent pointing at it and hides the composer's AI button. Nothing is lost: re-enabling the integration restores both.
Models
The model list is read live from the provider's API using your key — Pingo keeps no fixed catalog. If the key is not allowed to list models, it still generates: enter the model manually.
What can I do with an integration?
On this screen, you can:
- View which applications are integrated
- Identify the source of access (e.g., plugin, system, API)
- Control which applications have access to Pingo Notify
- Revoke integrations that should no longer access the system
Important to know
If an integration is removed or disabled,
the linked application immediately loses access to Pingo Notify.
This does not remove connections or messages; it only blocks the application’s access.
Summary
- Integration = application access authorization
- WordPress plugin is an example of an integration
- Integrations access connections and plan resources
- Without an integration, the application does not work
Before an application can send messages or manage connections, it must be integrated with Pingo Notify.