Bubble + Bento

Overview

Bento’s Bubble plugin enables secure, server-side actions so your Bubble application can:

• Track events (page milestones, purchases, onboarding steps, etc.).
• Create or update subscribers and their tags/fields.
• Send transactional emails from Bubble workflows.
• Keep Bento and Bubble data in sync in real time.

Prerequisites

• Active Bento account with API keys (publishable + secret) and the target site UUID.
• Bubble app with permissions to install marketplace plugins.

Setup Guide

1. In Bubble, open Plugins → Add plugins and search for “Bento”.
2. Install the Bento plugin.
3. In the plugin settings panel, provide:
   • publishable_key
   • secret_key
   • site_uuid
4. Repeat the values inside the Test fields if you maintain a staging Bento site.
5. Keep keys server-side—never expose them in client code.

Note: Store separate API keys per environment and limit access to trusted collaborators.

Available Actions

1. Bento – Send Event (Dynamic)

• Category: Data (Things)
• Purpose: Track user actions and automatically create/update subscribers.
• Required fields:
  • email (dynamic text)
  • type (static text such as $completed_onboarding, $purchase, etc.)
• Optional fields: detail_data (JSON), first_name, last_name, company_name, job_title, phone_number, source, status.

email: Input Email's value
type: "$completed_onboarding"
first_name: Input First Name's value
detail_data: {"plan": "pro", "seats": 10}

2. Subscriber Action

• Category: Data (Things)
• Purpose: Run simple commands against a subscriber.
• Required fields: email, command
• Commands: subscribe, unsubscribe, add_tag, remove_tag, add_field, remove_field
• Optional fields: query (tag/field value), field_name, field_value

Use Subscriber Action for lightweight changes. For bulk or multi-field updates, prefer Subscriber Update.

3. Subscriber Update

• Category: Data (Things)
• Purpose: Bulk update subscriber data during imports or major workflow checkpoints.
• Required field: email
• Optional fields: first_name, last_name, tags, remove_tags, custom_fields

Subscriber Update batches changes. Allow a short delay for Bento to apply everything.

4. Bento Transactional

• Category: Data (Things)
• Purpose: Send transactional email through Bento directly from Bubble.
• Required fields: to, from (must be an existing Bento author), subject, html_body, transactional
• Optional fields: text_body, personalizations (JSON payload)

to: "user@example.com"
from: "noreply@yourcompany.com"
subject: "Welcome to our platform!"
html_body: "<h1>Welcome {{name}}!</h1><p>Thanks for signing up.</p>"
personalizations: '{"name": "Ava", "link": "https://example.com"}'

Best Practices

Event Tracking

• Use descriptive event names (for example $purchase, $signup, $completed_onboarding).
• Include detail_data so journeys can branch by plan, SKU, or step.
• Keep naming consistent across Bubble and Bento.

Subscriber Management

• Validate email addresses before making updates.
• Use namespaced tags (product:pro, onboarding:complete) for clarity.
• Handle unsubscribe requests promptly.

Transactional Email

• Include both HTML and text bodies.
• Use personalization payloads for dynamic content.
• Secure forms with CAPTCHA/rate limiting before triggering transactional sends.

Security

• Never expose Bento API keys in client-side code.
• Validate every field that flows into Bento.
• Use HTTPS for any webhook or API call.

Common Use Cases

User Registration

1. User signs up inside Bubble.
2. Run Subscriber Update to add the new user into Bento.
3. Trigger Send Event with $signup.
4. Bento automation sends welcome email and starts the onboarding journey.

E-commerce Purchase

1. Workflow records an order.
2. Send Event with $purchase + order details.
3. Trigger Bento flows for receipts, fulfillment, and cross-sells.

Engagement Milestones

1. Workflow detects onboarding completion.
2. Send Event $completed_onboarding.
3. Apply an “onboarded” tag and trigger the next-step automation.

Troubleshooting

Error Handling & Advanced Notes

• Bento returns detailed error messages—log them in Bubble for quick triage.
• Rate limiting: space out bulk updates or queue actions inside Bubble.
• Custom fields: Subscriber Update automatically maps any extra keys you include.
• Tag management: pass comma-separated lists for tags/remove_tags; Bento creates missing tags automatically.

Support

• Email: support@bentonow.com
• Discord: Bento Community