Connect Ruby on Rails to Bento
Connect Ruby on Rails to Bento
Ready to dive deeper?
Explore our comprehensive Rails Sdk integration documentation and examples to get the most out of your automation.
Everything you need to ship fast
Rails‑native
simple initializer
Events & purchases
Flows on save
Background jobs
Sidekiq/Resque
Newsletters + transactional
one place
Your Rails app is already tracking users. Now turn that data into revenue.
Every signup, purchase, and interaction can trigger personalized campaigns that keep customers engaged and drive repeat business. The Bento Rails SDK makes it happen with Ruby-native integration.
to first automation
visual automation builder
higher customer lifetime value
Built for Rails developers who follow convention over configuration
Gem Install Ready
Install via RubyGems, works with Rails conventions and Active Record callbacks.
Real-time Event Capture
Stream events directly into Bento with ActiveJob and background processing via Sidekiq.
Enterprise Security
Built with Rails security best practices and enterprise-grade data protection.
Multi-Environment Support
Works with development, staging, and production environments seamlessly.
Everything you need for Ruby on Rails email marketing and automation
Rails‑native
simple initializer
Events & purchases
Flows on save
Background jobs
Sidekiq/Resque
Newsletters + transactional
one place
gem 'bento-sdk'
Get up and running with our official Rails SDK in seconds. Full Ruby support and comprehensive documentation included.
Track custom events
Send custom events like user_signed_up, order_completed, page_viewed with clean Ruby hashes.
Bento SDK integrates with your Rails stack
Works beautifully with the gems and platforms you're already using in your Ruby on Rails applications.
Perfect for Ruby on Rails apps
Background job processing
Heroku & cloud deployment ready
Idiomatic Ruby code included
Get started in 3 simple steps
Install
gem install bento-sdkAdd the official SDK or connect the integration.
Configure
rails credentials:edit && set BENTO_API_KEY=...Add your keys and basic settings.
Send your first event
Bento.track(event: 'user_signed_up', email: 'user@example.com')Trigger a Flow and see it live.
Real ways teams use this
Welcome series
Send a warm welcome on account creation.
event: user_signed_up → welcomeAbandoned cart
Rescue near‑purchases.
event: checkout_started → rescueDunning
Automate failed payment comms.
event: billing_failed → dunningNewsletter
Ship weekly updates to segments.
broadcast: newsletter → segment: activeTired of your current email provider?
No hassle. No surprises. Just better email.
Explore more integrations
Connect Bento with your entire tech stack. Choose from our comprehensive library of SDKs, platform integrations, and framework guides.
Development Kits
.NET SDK
ASP.NET & Web API tracking
Elixir SDK
Phoenix & OTP tracking
Go SDK
High-performance tracking
JavaScript SDK
Client-side tracking
Laravel SDK
Eloquent & Artisan tracking
Next.js SDK
React & SSR tracking
Node.js SDK
Server-side tracking
PHP SDK
Web application tracking
Python SDK
Django & Flask tracking
Rust SDK
Systems-level tracking
Supabase SDK
Database event tracking
Swift SDK
iOS & macOS tracking
WordPress SDK
Plugin development tracking
Platform Integrations
Bento Forms
Native form builder
Bubble
No-code app integration
ClickFunnels
Sales funnel automation
Google Tag Manager
Tag management system
Make
Workflow automation
n8n
Open-source automation
Segment
Customer data platform
SendOwl
Digital product sales
Shift4Shop
E-commerce platform
Shopify
E-commerce automation
SMS & WhatsApp (Twilio)
Multi-channel messaging
Stripe
Payment processing events
Tracking Script
Universal web tracking
Webflow
Visual web design
Webhooks
HTTP event callbacks
WooCommerce
WordPress e-commerce
WordPress
CMS integration
Zapier
App automation platform
Don't see your tech stack? We're always adding new integrations. Contact us on Discord to request help with an integration.
Frequently Asked Questions
Rails versions?
Supports modern LTS Rails. See docs for matrix.
Where do I call it?
Controllers, jobs, or service objects.
Is it thread‑safe?
Use one client per request/job for safety.