How to decide between using the API Connector or a plugin for API calls in Bubbl

Before choosing an approach, write down exactly what you need: Which external service? What actions do you need (read data, write data, trigger events)? How often will it run? Does it need to work in real-time or can it be batched? For example, if you need Stripe payments, you need: create charges, handle webhooks, manage customers. If you need weather data, you only need: read current weather for a location. Simple read-only integrations lean toward API Connector. Complex integrations with UI elements (like Stripe Checkout) lean toward plugins.

Go to the Plugins tab and click Add plugins. Search for the service you want to integrate. For each plugin you find, check these criteria: (1) Number of installs — higher is better, indicating community trust. (2) Last updated date — plugins not updated in 6+ months may not work with current Bubble. (3) Reviews and ratings — read negative reviews for specific issues. (4) Developer reputation — click the developer name to see their other plugins. (5) Pricing — one-time vs monthly subscription. (6) Documentation — does the plugin page explain setup clearly? A plugin with thousands of installs, recent updates, and good reviews is usually a safe bet.

Open the external service's API documentation (usually at docs.servicename.com or developer.servicename.com). Check: (1) Does it offer a REST API with JSON responses? Bubble's API Connector only works with REST/JSON. (2) What authentication method does it use? API Connector supports API keys, OAuth2, JWT, and Basic Auth. (3) How many endpoints do you need? If you only need 1-2 calls, the API Connector is straightforward. If you need 10+, a plugin saves time. (4) Is the API well-documented with examples? Good docs make API Connector setup much easier.

Use this framework to choose: GO WITH A PLUGIN when the plugin is well-maintained (updated recently, 1000+ installs), the integration requires custom UI elements (payment forms, chat widgets, map embeds), OR you need complex OAuth flows that the plugin handles automatically. GO WITH API CONNECTOR when no quality plugin exists, you need only 1-3 specific API calls, the plugin is expensive and you only use a fraction of its features, OR you want full control over the request/response without third-party dependency. GO HYBRID when you use a plugin for its UI components but supplement with API Connector calls for endpoints the plugin does not cover.

If you choose the API Connector path, go to the Plugins tab, find the API Connector (pre-installed), and click Add another API. Give it a name matching the service (e.g., 'Weather API'). Add your authentication — for API key auth, click Authentication → Private key in header, and enter your key. Add a new API call: name it (e.g., 'Get Current Weather'), set the method to GET, enter the endpoint URL, and add any parameters in brackets like [city]. Click Initialize call to test it. Bubble will map the JSON response structure so you can use the data in your app. Set 'Use as' to Data if you want to display results, or Action if you want to trigger it in workflows.