Monday.com

Before touching Bubble, you need two pieces of information from Monday.com: your API token and the numeric ID of the board you want to connect. To generate your API token: log in to Monday.com → click your avatar or profile photo in the bottom-left corner → select 'Developers' → under 'My Access Tokens', click 'Show' next to the v2 token → copy the full token string. This token gives the same access permissions as your Monday.com account, so keep it secure. To find your board ID: open the board in Monday.com and look at the URL in your browser. It will look like monday.com/boards/1234567890. The number at the end is your board ID. Write it down — you will use it directly in the GraphQL query body in a later step. If you have multiple boards for different clients or projects, note each board ID. You can build a Bubble dropdown that lets users select which board to view, with the board IDs stored in a Bubble Data type. For now, start with one board to confirm the connection.

Now set up the Monday.com connection in Bubble's API Connector. This is where you configure the two shared headers that all Monday.com calls will use. In your Bubble editor, click 'Plugins' in the left sidebar → click 'Add plugins' → search for 'API Connector' → click Install on the plugin by Bubble. Once installed, click 'API Connector' in the plugins list to open its configuration panel. Click 'Add another API' to create a new API group. Name it 'Monday.com'. Under 'Authentication', choose 'Private key in header' if the option appears, or leave as 'None' and add headers manually. In the 'Shared headers' section, add two headers: Header 1: Key = Authorization, Value = Bearer YOUR_TOKEN_HERE (replace YOUR_TOKEN_HERE with the token from Step 1). Check the 'Private' checkbox next to this header — this is critical. The Private flag means Bubble sends this header from its servers and it never appears in browser requests. Header 2: Key = Content-Type, Value = application/json. This header does NOT need to be Private — it is not sensitive. Leave the base URL field empty — with GraphQL you will use the full URL in each individual call since there is only one endpoint anyway.

1{
2  "shared_headers": [
3    {
4      "key": "Authorization",
5      "value": "Bearer YOUR_MONDAY_API_TOKEN",
6      "private": true
7    },
8    {
9      "key": "Content-Type",
10      "value": "application/json",
11      "private": false
12    }
13  ]
14}

Create your first API call — a query that lists your boards. This verifies that the token works and gives you a call you can reuse for board selection dropdowns. In the Monday.com API group, click 'Add a call'. Name it 'Get Boards'. Set the method to POST and the URL to https://api.monday.com/v2. In the Body section, check 'Send arbitrary data' — this allows you to send raw JSON. In the body text area, paste: {"query": "{ boards(limit: 20) { id name description } }"} This GraphQL query fetches the first 20 boards with their IDs, names, and descriptions. Set 'Use as' to 'Data' — this tells Bubble the call returns data you want to display, not just trigger an action. Click 'Initialize call'. Bubble will send the request to Monday.com and receive a real response. If initialization succeeds, you will see detected fields like data > boards > id, name, description. If you see an error: - 401 Unauthorized: check that the Authorization header value is 'Bearer TOKEN' (with the space) and that Private is checked. - 200 with empty boards array: you have a valid token but no boards are visible to this token — confirm the token belongs to an account with boards. After successful initialization, Bubble maps the response automatically. Click 'Save'.

1{"query": "{ boards(limit: 20) { id name description } }"}

Now add the call that fetches items from a specific board, including selected column values. This is the call your Repeating Group will use to display board data. Add another call in the Monday.com group. Name it 'Get Board Items'. Method: POST. URL: https://api.monday.com/v2. Check 'Send arbitrary data'. In the body, use the following query — replace 1234567890 with your actual board ID, and replace 'status' and 'person' with the actual column IDs from your board: {"query": "{ boards(ids: [1234567890]) { items_page { items { id name column_values(ids: [\"status\", \"person\"]) { column { title } text } } } } }"} The column IDs (like 'status', 'person', 'date4') are not the display names — they are internal identifiers. To find them: in Monday.com, open the board → click the three-dot menu on a column → 'Column settings' → the ID appears at the bottom, or check the URL when you hover the column header. Always use column_values(ids: [...]) with explicit IDs rather than column_values without filtering. Requesting all columns on a large board returns a 'ComplexityBudgetExhausted' error because Monday.com charges complexity units per field returned. Set 'Use as' to 'Data'. Click 'Initialize call'. Bubble detects the nested structure: data > boards > items_page > items > each item with id, name, and column_values. Map the column_values text field to the display you need in your Repeating Group.

1{
2  "query": "{ boards(ids: [1234567890]) { items_page { items { id name column_values(ids: [\"status\", \"person\"]) { column { title } text } } } } }"
3}

To let users create Monday.com items from a Bubble form, you need a GraphQL mutation call. This is how you write data back to Monday.com. Add a new call in the Monday.com group. Name it 'Create Item'. Method: POST. URL: https://api.monday.com/v2. Check 'Send arbitrary data'. The mutation body looks like this: {"query": "mutation { create_item (board_id: <BOARD_ID>, item_name: \"<ITEM_NAME>\") { id name } }"} However, you want the item name to be dynamic (coming from a Bubble input). Switch the 'Use as' setting to 'Action' — this means the call is triggered by a workflow step, not data display, and it can accept dynamic values from Bubble's workflow expression editor. Make the item name a dynamic parameter: in the body, replace the hardcoded item name with <dynamic value - ITEM_NAME> using Bubble's parameter syntax. Bubble will prompt you to set this value when you use the call in a workflow. For adding column values (such as setting a status or assigning a person when creating the item), the body includes a column_values argument as a JSON string: {"query": "mutation { create_item (board_id: 1234567890, item_name: \"<ITEM_NAME>\", column_values: \"{\\\"status\\\": {\\\"label\\\": \\\"New Request\\\"}}\") { id name } }"} The nested escaping looks intimidating but follows a consistent pattern: the column_values argument is a JSON string, so the inner JSON must be escaped with backslashes within the GraphQL argument string. Click 'Initialize call' with a test item name — initialization creates a real item in Monday.com. Check your board after initializing to confirm the item appears, then delete the test item manually.

1{
2  "query": "mutation { create_item (board_id: 1234567890, item_name: \"Test Item from Bubble\", column_values: \"{\\\"status\\\": {\\\"label\\\": \\\"New Request\\\"}}\") { id name } }"
3}

With your API calls initialized, wire everything together in the Bubble editor to create a working board view and form submission flow. For the board view Repeating Group: drag a Repeating Group element onto your page. In its data source, select 'Get data from an external API' → choose 'Monday.com - Get Board Items'. Set 'Data source' to the items array returned by the call. In the Repeating Group's cell, add Text elements and bind them to 'Current cell's Monday.com - Get Board Items's name' and the column_values text field for status and person. For form submission: add Input elements for the item name and any other fields. Add a Button. In the Button's Workflow, add the action 'Plugins → Monday.com - Create Item'. Set the ITEM_NAME parameter to the value of your name Input element. You can chain additional steps — for example, after creating the item, run 'Refresh data source' on the Repeating Group so the new item appears immediately. For privacy: if your Bubble app stores any Monday.com item data in a Bubble database table, go to Data tab → Privacy → set rules on that data type so only authorized users can read the stored items. Bubble's Privacy rules are the main guardrail against users accessing each other's data. For WU economy: Monday.com data that does not change frequently (board names, team structures) can be cached in a Bubble database table, refreshed on a schedule via a Backend Workflow (paid plan), rather than fetched live on every page load. This reduces both WU consumption and API complexity usage. RapidDev's team has built hundreds of Bubble apps with integrations like this — if you need help designing the full Monday.com portal architecture, book a free scoping call at rapidevelopers.com/contact.