Skip to main content
AIWA supports a growing set of connectors for payments, email, communications, media, AI providers, scheduling, calendars, meetings, and file workflows. But you may need a service that isn’t currently available as a built-in connector. In that case, you can request a new connector. Tell us which service you need, what you want to build with it, and why it matters to your workflow.

​
Before requesting a connector

First, check whether AIWA already supports the capability you need through an existing connector. For example: Sometimes the service you want isn’t necessary if another supported connector already solves the underlying product requirement.

​
Request the capability, not just the brand

When requesting a connector, tell us what you’re trying to accomplish. Instead of:
Add HubSpot.
Tell us:
We use HubSpot as our CRM and want AIWA applications to create contacts and deals when users submit forms.
That’s much more useful. Or instead of:
Add Dropbox.
Tell us:
Our agency stores client documents in Dropbox and we want client portals built with AIWA to display files associated with each project.
Understanding the use case helps us evaluate the integration properly.

​
What to include in your request

A useful connector request includes: Service Which product or API do you want AIWA to support? Use case What are you trying to build? Actions What should your AIWA application be able to do with the service? Frequency Is this needed for one project or something you use regularly? Business impact What does this integration unlock for you or your clients? For example:
That’s an excellent connector request.

​
Example requests

CRM
Please add HubSpot. We want lead forms built with AIWA to create contacts and deals inside our clients’ HubSpot accounts.
Automation
Please add Zapier. We want AIWA apps to trigger workflows that connect with tools not yet available as native connectors.
Accounting
Please add QuickBooks. We want invoices generated in our AIWA application to sync with our accounting workflow.
Storage
Please add Dropbox. We want customers to access files associated with their projects from inside an AIWA-built client portal.
Communication
Please add WhatsApp messaging. We want booking confirmations and customer updates to be sent through WhatsApp.
The more specific the workflow, the easier it is to understand what the connector needs to support.

​
Can AIWA use an API without a connector?

Sometimes a service may expose an API even when AIWA doesn’t yet have a dedicated connector for it. Depending on the service and your application, AIWA may be able to build a custom API integration. For example:
This service has a REST API. Review its API requirements and determine whether we can connect it to the application without a native AIWA connector.
For custom integrations, you may need to provide information such as:
  • API documentation
  • Authentication method
  • Required endpoints
  • Expected request and response formats
  • Webhook documentation
  • Rate limits
  • Required permissions
A custom API integration and a native AIWA connector are not necessarily the same experience. Native connectors are designed to simplify configuration and reuse across AIWA workflows.

​
Use Explore Mode first

If you’re unsure whether a custom integration is possible, use Explore Mode. For example:
We need to connect this application to HubSpot. We don’t currently have a native HubSpot connector. Analyze what would be required to integrate with HubSpot’s API. Don’t build anything yet.
AIWA can help you understand the integration surface before implementation.

​
Plan complex integrations

Some external services require more than one API request. For example, an accounting integration might involve:
  • Customers
  • Products
  • Invoices
  • Payments
  • Taxes
  • Webhooks
  • Authentication
  • Data synchronization
For integrations like these, use: Explore → Plan + Max → Review → Build rather than immediately attempting implementation.

​
Authentication requirements matter

External APIs can use different authentication methods. For example:
  • API keys
  • OAuth
  • Access tokens
  • Client credentials
  • Service accounts
If you’re requesting a connector, include any relevant information about how the provider authorizes applications. Don’t send secret credentials in the request itself.

​
Webhooks may be required

Some integrations need the external service to notify your application when something changes. For example:
If your intended workflow relies on real-time updates, include that in the connector request. For example:
When a deal changes stage in HubSpot, we need the associated record in our AIWA application to update automatically.
That’s very different from only creating HubSpot contacts.

​
Read vs write access

Explain whether your application needs to: Read Show customer information from the external service. Write Create or update information in the external service. or both. For example:
We need to read products from Shopify and create orders from our AIWA-built sales portal.
This helps define the connector requirements.

​
One-way vs two-way synchronization

Some integrations only need information to move in one direction. For example:
Others require two-way synchronization:
Two-way synchronization is significantly more complex because the application needs to determine what happens when information changes in either system. If you need synchronization, mention it explicitly.

​
Prioritizing connector requests

Connector requests help us understand which services AIWA users need most. When submitting a request, clearly explaining the business use case can help us evaluate its usefulness. A connector requested by many agencies for a repeatable workflow may have broader value than an integration needed for one unusual project. That doesn’t mean uncommon requests aren’t useful. It simply helps us understand the impact.

​
Requesting a connector

Use the connector request option available inside AIWA or contact AIWA Support with:
Do not include passwords, private API keys, or secret credentials in the request.

​
Security

Any new integration should be designed with appropriate credential handling and access controls. When requesting a connector:
  • Don’t send secret keys
  • Don’t send passwords
  • Don’t expose access tokens
  • Don’t include customer credentials
  • Share documentation links rather than private configuration
  • Describe the permissions the integration requires
Credentials should only be supplied through the appropriate secure configuration flow when the integration is actually being configured.

​
Need help now?

If the connector you need isn’t currently available and it’s blocking an active project, contact AIWA Support. Include:
  • The service
  • The project you’re building
  • The workflow you’re trying to implement
  • The required actions
  • A link to the service’s API documentation if available
We can then help determine whether:
  • An existing connector can solve the requirement,
  • A custom API integration may be possible, or
  • A new native connector is needed.

Publishing to a Live URL

Publish your AIWA project to a live URL customers can visit.