Dynamic Integrations
Connect Blaze to any third-party platform or tool that has an API -- no custom setup required.
What are Dynamic Integrations?
Dynamic Integrations let you connect Blaze to virtually any external service by simply providing an API key. Instead of relying on pre-built, platform-specific integrations, Blaze uses its agentic web use and code execution capabilities to interact with any API on your behalf.
Whether it's Notion, HubSpot, Google Drive, Jira, Intercom, or any other tool with an API - Blaze can work with it. Just give it the API key and tell it what you need.
How it works
When you add a Dynamic Integration, Blaze gains the ability to authenticate with that service's API. From there, it can flexibly interact with the platform in whatever way is needed to accomplish your goal. There's no rigid connector or limited set of actions. Blaze figures out how to use the API based on what you ask it to do.
Adding an integration
Navigate to Workspace Settings from the sidebar.
Scroll down to the Integrations section.
Click Add integration.
Fill in the following fields:
Name -- A recognizable name for the integration (e.g. "HubSpot", "Notion", "Google Drive").
API key -- The API key or access token from the service you want to connect.
Description (optional) -- A brief note about what this integration is for, which helps Blaze understand how to use it.
Click Add.
The integration is now available to your entire workspace.
Testing your integration
Once you've added an integration, the easiest way to verify it works is to ask Blaze a simple retrieval question. For example:
"Using HubSpot, show me my most recent contacts."
"Pull my latest documents from Notion."
"List the files in my Google Drive."
If Blaze successfully returns results, your integration is working correctly.
Tips for getting the most out of Dynamic Integrations
Use descriptive names. Naming your integration clearly (e.g. "HubSpot CRM" rather than "API 1") helps Blaze understand which service to use when you ask.
Add a description. A short description like "Our CRM for managing sales leads and contacts" gives Blaze additional context to work with the API more effectively.
Use the right API key permissions. Make sure the API key you provide has the necessary permissions for what you want Blaze to do. Read-only keys will limit Blaze to retrieving data, while read-write keys allow it to take actions on your behalf.
Be specific in your requests. The more specific your prompt, the better Blaze can determine how to use the API. Instead of "check HubSpot", try "show me all HubSpot deals closed this month".
Managing integrations
You can view all active integrations in the Integrations section of your Workspace Settings. To remove an integration, click the trash icon next to it and confirm the removal. Removing an integration revokes Blaze's access to that service immediately.
Who can manage integrations?
Dynamic Integrations are configured at the workspace level. Only workspace admins can add or remove integrations. Once added, the integration is available to all members of the workspace.
FAQ
Which services are supported?
Any service that provides an API key or access token for authentication. This includes most modern SaaS platforms, developer tools, and cloud services.
Is my API key stored securely?
Yes. API keys are stored securely in your workspace's configuration and are only used by Blaze when executing requests on your behalf.
Can I add multiple integrations?
Absolutely. You can add as many integrations as you need -- there's no limit.
What if Blaze doesn't know how to use a particular API?
Blaze is familiar with the APIs of most popular platforms. For less common services, adding a description to your integration and being specific in your prompts will help Blaze work with the API effectively.