AI Provider Integration Overview
Choose an AI provider, create a protected API credential, select a model, control spending and test Wemblo connectivity.
What this guide helps you do
Choose an AI provider, create a protected API credential, select a model, control spending and test Wemblo connectivity.
Who should use it
Workspace owners, managers, automation users and authorized technical users responsible for AI configuration or customer workflows.
Before you begin
- Use the correct workspace and minimum required role.
- Use a business-controlled provider account where applicable.
- Understand provider billing, usage and data settings.
- Use fictional Pakistan test data.
- Define human handover before enabling automatic replies or calls.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Provider Account | Business-controlled external account. |
| Project / Workspace | Provider container for billing and keys. |
| API Key | Secret credential. |
| Model | Selected AI model. |
| Provider Budget | External cost control. |
| Wemblo AI Limit | Plan or add-on capacity. |
Step-by-step instructions
- Compare provider availability, models, data terms and cost.
- Create a business provider account/project.
- Enable billing or credits if required.
- Create a restricted key.
- Enter it only in Wemblo.
- Select the model.
- Set provider and Wemblo usage controls.
- Test.
- Record rotation and revocation.
Test and verification
- Run one short factual test.
- Run one multilingual test.
- Review provider usage/billing.
- Confirm unauthorized users cannot see the key.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Unauthorized | Key, project and provider account. |
| Model missing | Provider/model access and Wemblo support. |
| Rate limit | Provider limit and request volume. |
| Cost spike | Model, volume, retries and output length. |
Security, privacy, consent, cost and provider notes
- AI-provider charges and Wemblo AI-action usage are separate controls.
- Do not expose provider keys or customer data in screenshots, tickets or client-side code.
- Use human review or handover for sensitive, private, regulated, urgent, high-value or final decisions.
- Do not promise perfect accuracy or guaranteed business outcomes.
Last reviewed:

