Using Multiple StackBloom Apps Together
StackBloom apps are designed to work with each other. Connect Proposals with E-Sign, pipe form submissions through Automations, and build end-to-end workflows across your stack.
Proposals → E-Sign Workflow
The most common StackBloom integration. Build a proposal in Proposals, then send it directly for e-signature — no copy-pasting or switching tools required.
How It Works
- Create and finalize your proposal in the Proposals builder
- Click "Send for Signature" directly from the proposal
- The proposal is passed to E-Sign with your content pre-loaded
- Place signature fields and assign signers in E-Sign
- Signers receive an email and complete the process in the browser
- Signed document and audit log are stored in both apps
Required: Active subscription to both Proposals and E-Sign.
Forms → Automations → InboxBridge Pipeline
Capture leads with Forms, process them with Automations, and route notifications to Slack or email via InboxBridge. This setup works well for sales and support teams.
Example: New Lead Pipeline
- Set up your form in Forms Builder and publish it
- In Automations, create a new workflow with trigger type "Form Submission"
- Select your form from the dropdown
- Add conditions and actions — including Slack or email via InboxBridge
- Activate the workflow
Scheduling + Google Calendar Sync
Connect StackBloom Scheduling to your Google Calendar so bookings appear automatically on your calendar and your availability stays up to date.
- Go to Scheduling Dashboard → Settings → Integrations
- Click "Connect Google Calendar" and complete the OAuth flow
- Select which Google Calendar to write new bookings to
- Optionally select calendars to check for conflicts (so double-bookings are prevented)
- New bookings will now appear in Google Calendar automatically
Two-Way Sync
When you mark yourself as busy on Google Calendar, StackBloom Scheduling will automatically block that time slot from being booked.
Sharing Data Between Apps
StackBloom apps share the same underlying account, which means data can flow between them via Automations workflows or direct integrations.
Common Data Sharing Patterns
Forms → SchedulingPre-fill booking details from a form submission (e.g., contact info)E-Sign → AutomationsTrigger a workflow when a document is fully signedScheduling → AutomationsSend a follow-up email sequence after a meeting is bookedProposals → AutomationsNotify your team when a proposal is viewed or acceptedIntegration Tips
Automations is the Hub
The Automations app is the central integration layer. If you want two apps to talk to each other, Automations is usually the bridge.
Test Before Activating
Always use Automations' test mode before activating a multi-app workflow to ensure data flows correctly between apps.
Webhooks for Custom Integrations
Most StackBloom apps support webhooks. Use these to integrate with external tools like Zapier, Make (Integromat), or your own systems.
Next Steps
Explore Automations
The visual workflow builder that connects all your StackBloom apps
Creating Workflows
Step-by-step guide to building your first automation workflow
Browse All Products
Discover all 13 StackBloom apps and how they fit together
Get Help
Contact support for help setting up cross-app integrations