Doodle

Before attempting any API Connector setup for Doodle, confirm that your use case does not require Doodle's API. Visit https://developer.doodle.com in your browser. If you attempt to register as a developer, you will encounter an enterprise partner requirement — standard developer accounts are not provisioned. This is the current state of Doodle's API access policy as of 2026. As a result, there is no standard Bubble API Connector setup for Doodle that will work for independent developers. Do not spend time trying to build an OAuth flow — the credential acquisition step is blocked before you can write a single line of configuration. Instead, decide which path fits your use case: **Choose the iframe embed if:** - You already have or will create Doodle polls manually in Doodle's interface - You just want Doodle's UI to appear inside your Bubble app - You do not need vote data in Bubble's database - You are prototyping or building an MVP and speed matters **Choose the custom Bubble poll if:** - You want all scheduling data in Bubble's database - You need to trigger workflows on new votes (send emails, update records) - You want to customize the scheduling UI with your own branding - You need to query or report on poll results from Bubble - You are building a production app used by real clients or team members **Choose Calendly if:** - Your primary need is one-on-one meeting booking (not group polls) - You want real calendar integration (Google Calendar, Outlook) - You want a fully functional REST API integration in Bubble The rest of this tutorial covers both the embed path (Steps 2–3) and the custom Bubble poll path (Steps 4–6).

If you have chosen the embed path, this step creates the Doodle poll view inside your Bubble page using Bubble's HTML element. First, create your Doodle poll in Doodle's own interface at doodle.com. Log in, click 'Create a Doodle', set up your time options, and publish the poll. Copy the poll participation URL — it looks like https://doodle.com/meeting/participate/id/{pollId} or a similar format depending on Doodle's current URL structure. In your Bubble editor, open the page where you want the poll to appear. Click the '+' button (Add elements) → HTML element. Draw the HTML element on the page at the desired size — Doodle's scheduling interface needs enough height to display time options comfortably (at least 500px tall is recommended). Click on the HTML element to open its properties and paste the following iframe code into the content field: ```html <iframe src="https://doodle.com/meeting/participate/id/{YOUR_POLL_ID}" width="100%" height="100%" frameborder="0" style="border: none; min-height: 480px;"> </iframe> ``` Replace {YOUR_POLL_ID} with the actual poll ID from your Doodle poll URL. Adjust the height value to fit your page layout. Limitations to communicate to users: the poll is rendered in an iframe served from Doodle's servers. Participants interact with Doodle's interface — Bubble does not receive any data about who voted or which options they selected. Doodle's branding appears inside your page. If Doodle changes its URL structure or embed policy, the iframe will break and you will need to update the embed code. There is no way to trigger a Bubble workflow when a participant submits their vote through this embed. For a branded, controlled scheduling experience where you capture vote data — proceed to Steps 4–6 for the custom Bubble poll.

1<iframe 
2  src="https://doodle.com/meeting/participate/id/{YOUR_POLL_ID}" 
3  width="100%" 
4  height="560px" 
5  frameborder="0" 
6  style="border: none; border-radius: 4px;">
7</iframe>

If you have chosen the embed path and want to show poll results (not just the voting view), Doodle provides a results URL for completed polls. The results view is accessible at a different URL format that shows the aggregated availability. In Doodle's interface, after participants have voted, navigate to the poll results page — Doodle shows a summary of which time slots have the most availability. The results page URL typically has a different format from the voting URL. In Bubble, add a second HTML element (or a toggle-able Group containing an HTML element) with the Doodle results URL embedded as an iframe. Add a Button labeled 'View Results' that toggles the visibility of the results Group versus the voting Group. For a tabbed interface: create two Groups — 'Voting View' and 'Results View' — each containing an HTML element with the respective Doodle iframe. Add a workflow triggered by a 'Show Results' button that hides the Voting View Group and shows the Results View Group. Important reminder: this entire embed approach means all scheduling logic lives in Doodle's system. Bubble's database has no record of poll participants, votes, or results. If you ever need to programmatically access this data (to send automated follow-up emails, integrate with a calendar, or archive results), you cannot do so through the embed — you would need the custom poll approach from Steps 4–6 instead. For the custom Bubble poll path, skip this step and continue to Step 4.

1<!-- Voting view iframe -->
2<iframe 
3  src="https://doodle.com/meeting/participate/id/{POLL_ID}" 
4  width="100%" height="560px" frameborder="0">
5</iframe>
6
7<!-- Results view iframe (different URL format) -->
8<iframe 
9  src="https://doodle.com/meeting/organize/id/{POLL_ID}" 
10  width="100%" height="560px" frameborder="0">
11</iframe>

The custom Bubble poll gives you full control: all data lives in your Bubble database, you can query it in workflows, and you can build any UI you want. Start by creating the two core Data Types. Go to the Data tab in the Bubble editor. Click 'Add a type'. **Data Type 1: SchedulingPoll** Fields to add: - title (text) — the poll's name or meeting title - organizer_email (text) — who created the poll (for notification purposes) - time_slots (list of text) — the proposed time options (e.g., ['Mon Jan 12 10am', 'Mon Jan 12 2pm', 'Tue Jan 13 11am']). Using a list of text allows flexible slot descriptions. - expiry_date (date) — when voting closes - unique_id (text) — a randomly generated ID for the shareable link (use Bubble's 'Generate random string' or a UUID to populate this on creation) - is_closed (yes/no) — whether the organizer has closed voting **Data Type 2: SchedulingVote** Fields to add: - poll (SchedulingPoll) — which poll this vote belongs to - participant_name (text) — voter's name - participant_email (text) — voter's email (used for duplicate prevention) - selected_slots (list of text) — which time slots the participant marked as available - created_date (date) — timestamp of the vote **Privacy rules:** Go to Data tab → Privacy for each type. For SchedulingPoll: add a rule — 'Everyone can see this field' for title, time_slots, expiry_date, unique_id, and is_closed. Restrict organizer_email to 'logged in users only' or hide it entirely from the voting UI. For SchedulingVote: allow anyone to create a new vote (for anonymous voting); restrict search/list to 'logged in users only' (organizers only see all votes — participants do not see each other's responses). Add a constraint: 'Only when the voter's email field doesn't equal an existing vote's email for the same poll' — this is enforced in the workflow, not the privacy rule.

With the Data Types in place, build two pages: a Poll Creation page for organizers and a Voting page for participants. **Poll Creation Page (page name: create-poll)** Add the following elements: - An Input element for Poll Title (connected to a Custom State: poll_title) - An Input element for Organizer Email - A Date Picker for Expiry Date - A Repeating Group or a dynamic text input section for time slots — simplest approach: add 5 Input elements (Slot 1 through Slot 5) and let the organizer fill in as many as they want. Or use a Repeating Group with a Custom State list that starts with 3 slots and an 'Add another slot' button - A Button labeled 'Create Poll' Poll creation workflow (triggered by the 'Create Poll' button): 1. Action: Create a new SchedulingPoll → set title = Poll Title input's value, organizer_email = Organizer Email input's value, expiry_date = Date Picker's value, time_slots = list of all non-empty slot inputs, unique_id = generate a random string (use Bubble's 'Random string' feature or a workflow expression that combines timestamp + random characters), is_closed = 'no' 2. Action: Navigate to the Voting page (see below) with the new poll's unique_id as a URL parameter 3. Optional: Copy-to-clipboard workflow that generates the shareable voting link: https://yourapp.bubbleapps.io/vote?poll_id={unique_id} **Voting Page (page name: vote)** This page receives the poll's unique_id as a URL parameter (page parameter: poll_id). Use 'Get data from page URL' to fetch the matching SchedulingPoll where unique_id = URL parameter poll_id. Add these elements: - A Text element showing the poll title (from the found SchedulingPoll) - A Repeating Group displaying the SchedulingPoll's time_slots list. Each cell shows the slot text and a Checkbox element. - Input fields for participant_name and participant_email - A Button labeled 'Submit My Availability' Voting workflow (triggered by 'Submit My Availability'): 1. Condition check: search for SchedulingVotes where poll = current SchedulingPoll AND participant_email = the Email input's value. If this count > 0, show an alert: 'You have already submitted your availability for this poll.' Stop the workflow. 2. Condition check: if the SchedulingPoll's is_closed = yes or expiry_date < Current date/time, show an alert: 'This poll is closed.' Stop the workflow. 3. Action: Create a new SchedulingVote → set poll = found SchedulingPoll, participant_name = Name input, participant_email = Email input, selected_slots = list of all Checkbox cells where the checkbox is checked (collect the time_slot text from each checked cell), created_date = Current date/time 4. Action: Show a confirmation message: 'Thank you! Your availability has been recorded.' RapidDev's team has built custom scheduling tools in Bubble for service businesses and team coordination apps — if you need to extend this poll with calendar sync or automated email reminders, get a free scoping call at rapidevelopers.com/contact.

The Results page shows the organizer (and optionally participants) which time slot has the most availability. Create a new page named 'poll-results' that accepts the poll's unique_id as a URL parameter. Fetch the SchedulingPoll: use 'Get data from page URL' → search SchedulingPoll where unique_id = URL parameter poll_id. Display vote summary: add a Repeating Group with the SchedulingPoll's time_slots list as data source. In each cell: - Show the slot text (current cell's text value from the time_slots list) - Show the vote count for this slot: 'Do a search for SchedulingVotes where poll = current SchedulingPoll AND selected_slots contains current cell's text' → count - Show a visual indicator — a progress bar Group whose width is proportional to (this slot's vote count / total participant count × 100%) Sort the Repeating Group by vote count descending to show the most popular slot first. Since Repeating Groups sorted by a calculated value (not a stored field) can be tricky in Bubble, consider storing the vote counts in a custom state or using a 'Sorted by' custom expression. Total participant count: display 'Do a search for SchedulingVotes where poll = current SchedulingPoll' → count. Winning slot announcement: add a Text element visible only when vote data is loaded: 'Best availability: [slot with highest vote count]'. Use a conditional to show this only when at least one vote exists. Close poll button: add a Button labeled 'Close Voting' visible only to the organizer (add a condition: current page's URL parameter 'organizer' = a value set when creating the poll, or use Bubble's User auth if organizers log in). The workflow: make changes to SchedulingPoll → set is_closed = yes. Privacy consideration: the Results page should be accessible to anyone with the poll link if you want participants to see the aggregate results. If results should be organizer-only, add a URL parameter check or require login. For anonymous public polls, make the Results page publicly accessible but ensure individual votes (SchedulingVote records) are not directly queryable from the public-facing UI — only the aggregate counts.