Once your connector and its Data Resources are fully configured, the bridge is ready. The true power of Mogno is that you can now leverage this integration conversationally within your applications, without writing a single line of code.
This guide explains the complete end-to-end execution flow—from assigning permissions to populating your production tables—and provides best practices for performance and troubleshooting.
The App Integration & Execution Flow
Creating a Data Resource is only half the journey. To actually use this connection—whether you are fetching data in real-time or storing it in an internal database—you must integrate it into an application.
Mogno does not automatically execute endpoints in the background just because a connector was created. To bring your integration to life, follow these four chronological steps:
Step 1: Application Assignment
When creating or editing your Data Resource in the Connectors tab, ensure you selected your target application in the Application Access list. Without this, the application will not have permission to consume the connector. (Note: If you are configuring the connector before your app exists, you can skip this and return to edit the connector later).
Step 2: Building Interfaces & Events with Monica
Open your application in the AI Solutions Builder and interact with Monica. She acts as your orchestrator, fully aware of the connectors your application has permission to access. You do not need to manually drag and drop data blocks. Simply ask her in natural language to set up the interface and the Event (such as clicking an “Update” button, or automatically when a specific screen or modal opens) that will execute the endpoint.
Pro-Tip for Prompts: Always mention the specific name of your connector in your prompt so Monica knows exactly which integration to use.
Here are just a few examples of the endless possibilities you can ask her to build:
- Example 1: Populating UI Elements (Dashboards & Lists)
Tell Monica what information you want to see. Prompt Idea: “Create a modal to register a new sale, and use the ‘HubSpot CRM’ connector to automatically populate the ‘Select Company’ dropdown menu with a list of our active clients when the modal opens.” - Example 2: Real-Time Calculations & Conversions
Fetch live utility data to power your application’s internal logic. Prompt Idea: “Use the ‘Exchange Rates’ connector to fetch the live USD to EUR currency rate and automatically convert the total value of this invoice on the screen.” - Example 3: Sending Data (Forms & Actions)
If you need to send information back to the external system, ask her to build input methods. Prompt Idea: “Create a form to register a new lead and map the ‘Submit’ button to execute the ‘Salesforce’ connector.” - Example 4: Automated Workflows
If you need data to sync in the background based on app events, ask her to build an automation. Prompt Idea: “Create a background workflow that automatically pushes the client data to the ‘Oracle ERP’ connector whenever a contract status changes to ‘Approved’.”
Step 3: Testing in Preview Mode
Before publishing, use the View icon (Preview mode) to interact with your app as a user would. Perform the action Monica configured (e.g., open the modal or click the specific button) to execute the connector and ensure the data loads correctly on the screen.
Important Note on Preview Mode: Data changes made here are not reflected in the published app, and lists are limited to displaying up to 30 records. Additionally, if you chose the “Store data for this resource” option, be aware that Preview mode will not populate your destination table.
Step 4: Publishing and Execution
Once published, open the live application and perform the action that calls the data (e.g., load the screen or click your new button). The connector will execute and display the live data to your users.
Why is my Data Table empty?
If you selected the “Store data for this resource” option during setup, this exact moment (the first live execution) is when your destination table is populated for the first time and the full dataset becomes available. If you disabled that option (Real-Time data), the information simply flows to the screen and your tables will naturally remain empty.
Golden Rules for Performance
Almost all modern platforms enforce Rate Limits (a strict limit on how many requests you can make per minute or hour). To keep your apps running smoothly and avoid blocks, always follow these best practices:
1. Never Fetch “Everything”
Avoid creating GET resources that simply download the entire database without limits. Always use the Request Parameters to filter the query (e.g., fetch records where status = active and limit = 50).
2. Store Heavy Data Locally
As explained during the setup, if you are building a dashboard or displaying long lists of records, you should enable “Store data for this resource” to read from Mogno’s internal database instead of pinging the external API constantly.
3. Ask Only for What You Need
Some external APIs allow you to specify exactly which fields you want returned (often through a fields parameter). If your app only needs to display a user’s name and email, request only those fields to speed up the data transfer.
Troubleshooting Common Errors
If a widget built by Monica is completely empty or fails to execute an action, verify your permissions. Return to the Connectors tab, edit the endpoint, and ensure your current app is checked in the Application Access list.
If the permissions are correct but it still fails, click the Test Data Source button on your endpoint to see what the external API is responding with.
Important Disclaimer on Error Codes:
Mogno acts as a transparent bridge, passing along the exact status and error message returned by the external system. The table below outlines the standard HTTP error codes as a helpful guide. However, because every external platform is built differently, they may occasionally use custom codes or deviate from these standard conventions. Always consult the specific external API’s documentation for the absolute source of truth if an error persists.
| Error Code | What it means | How to fix it |
|---|---|---|
| 401 Unauthorized | The external system rejected your access. | Your API Key might have been revoked, your OAuth token expired, or you typed the password incorrectly. |
| 403 Forbidden | Your credentials are valid, but you don’t have permission to see this specific data. | Check the permissions of the user/account in the external system. |
| 404 Not Found | Mogno reached the server, but the specific endpoint doesn’t exist. | Check your configuration. You likely have a typo in the URL Path. |
| 429 Too Many Requests | You have hit the external system’s Rate Limit. | Your app is making too many calls too fast. You must wait for the block to lift. |
Video Tutorial: End-to-End Practical Example
To tie everything together, watch the video below to see a full connector setup in action. We will connect Mogno to Open Exchange Rates, a financial API, to fetch live USD conversion rates and display them in our application.
Quick Reference: Setup Values (Click to expand)
If you are following along with the video, here are the exact values you need to copy and paste into your Custom Connector:
1. Settings Tab
| Field | Value |
|---|---|
| Protocol | HTTPS |
| Base URL | https://openexchangerates.org/api |
| Authentication Method | API Key |
| Key | Paste your generated App ID here |
| HTTP Verb | GET |
2. Data Resources Tab
| Field | Value |
|---|---|
| URL Path | /latest.json |
| HTTP Verb | GET |
| Query Parameter | Key: app_id / Value: Paste your App ID here |
| Store Data | Enabled |
| Destination Table Name | exchange_rates |
3. Monica Prompt (Inside your App)
“Use the ‘Get Latest Exchange Rates’ connector to fetch the current USD exchange rates and display them in a table showing the currency code and rate.”
Conclusion: You Are Ready!
Congratulations! You have successfully navigated the entire lifecycle of a Mogno Connector. From configuring secure authentication and translating complex API documentation into Data Resources, to mastering database architecture and troubleshooting external errors.
By combining these robust backend bridges with Monica’s conversational building capabilities, your workspace is now a truly integrated, automated ecosystem.
Now it is your turn! What external systems are you connecting to Mogno? Did you run into any unique API challenges while setting up your endpoints? Share your use cases, ask questions, or help other builders by replying to this thread. Let’s build together!