Integrations Overview

Buildorado integrates with 27 third-party services so you can connect your forms and workflows to the tools your team already uses. Every integration authenticates through OAuth 2.0, stores credentials with AES-256 encryption, and becomes available across all workflows in your workspace the moment you connect. Whether you need to collect payments with Stripe, send notifications to Slack, create calendar events in Google Calendar, or push data to a custom API via webhooks, Buildorado handles the connection so you can focus on building your process.

How Integrations Work in Buildorado

Integrations in Buildorado follow a connect-once, use-everywhere model. You authenticate a service in your workspace settings, and that connection is immediately available as an action node on the workflow canvas. When a user submits a form or a workflow executes, Buildorado calls the connected service on your behalf using the stored credentials. There is no code to write, no API keys to manage manually, and no middleware to maintain.

Each integration exposes one or more actions you can drop onto the canvas. For example, the Slack integration gives you a "Send Message" action, while Google Sheets gives you "Append Row" and "Read Range" actions. You configure each action using a point-and-click interface and inject dynamic data from earlier form fields and nodes using the {{variableName.property}} template syntax.

Available Integrations by Category

Messaging and Notifications

Messaging integrations are ideal for real-time notifications. For example, you can alert your sales team in Slack whenever a high-value lead submits a form, or notify a support channel when a new ticket arrives. Use conditional logic to route messages to different channels based on form responses.

Email

The built-in email action uses Resend for high-deliverability transactional email. You can design HTML emails with dynamic content from your form submissions, include file attachments, and send to multiple recipients. For Microsoft environments, the Outlook Mail integration sends from your organization's M365 account.

CRM and Sales

CRM integrations let you push form submissions directly into your sales pipeline. Map form fields to CRM properties and create new records automatically. This eliminates manual data entry and ensures every lead is captured instantly.

Project Management

Project management integrations bridge the gap between user-facing forms and internal workflows. Accept bug reports, feature requests, or internal requests through Buildorado forms, then automatically create issues or tasks with all the submitted data pre-populated.

File Storage

File storage integrations handle the documents your forms collect. When a user uploads a resume, signed contract, or supporting document through a file upload field, Buildorado can automatically store it in the right folder in Google Drive, OneDrive, or other cloud storage.

Spreadsheets

Spreadsheet integrations are the simplest way to collect structured data. Every form submission can append a new row to a Google Sheet or Excel workbook, with each form field mapped to a column. This gives your team a familiar interface for reviewing and analyzing submissions.

Calendar and Scheduling

Calendar integrations automate appointment booking and event scheduling. Combine a date/time field in your form with a Google Calendar action to create events instantly when users submit.

Analytics

Analytics integrations let you feed form submission data directly into business intelligence tools. Build live dashboards that update in real time as new submissions arrive.

Payments

Payment integrations embed checkout directly into your form flow. Users enter payment details as a step in the form, and the charge is processed before the workflow continues. See the Payment Integrations for configuration details, subscription setup, and test mode.

Custom and Developer Tools

For any service that does not have a native integration, webhooks and the HTTP Request node let you connect to any REST API. Send JSON payloads with dynamic data, authenticate with API keys or OAuth tokens, and handle the response in your workflow.

How to Connect an Integration

Setting up an integration takes less than a minute. Here is the step-by-step process:

1. Navigate to Settings > Integrations in your Buildorado dashboard.
2. Find the service you want to connect and click the Connect button.
3. A popup window opens for the service's OAuth 2.0 authorization screen. Sign in with your account for that service and grant Buildorado the requested permissions.
4. Once authorized, the popup closes and the integration status changes to Connected. You will see the connected account name or email.
5. The integration is now available in all workflows in your workspace. Drag an action node onto the workflow canvas and select the connected service.

You can connect multiple accounts for the same service. For example, you might connect a personal Google account and a company Google Workspace account, then choose which one to use in each workflow.

Managing Connections

Viewing Connected Integrations

The Settings > Integrations page shows all connected services with the account name, connection date, and status. A green indicator means the connection is active and credentials are valid.

Disconnecting an Integration

Click the Disconnect button next to any connected service to revoke access. This immediately invalidates the stored credentials and removes the connection from all workflows. Any workflow that uses that integration will fail at the disconnected action node until you reconnect.

Refreshing Credentials

Buildorado automatically refreshes OAuth tokens before they expire. If a token refresh fails (for example, because you revoked access from the service's side), the integration status changes to Expired and you will need to reconnect.

Security of Stored Credentials

Buildorado takes credential security seriously:

• Encryption at rest -- All OAuth tokens and API keys are encrypted with AES-256 using AWS KMS-managed keys before being stored in the database.
• Encryption in transit -- All communication between Buildorado and third-party services uses TLS 1.2 or higher.
• Minimal permissions -- Each OAuth integration requests only the scopes needed for the supported actions. Buildorado never requests full admin access unless the specific action requires it.
• No credential exposure -- OAuth tokens are never returned in API responses or visible in the dashboard UI. You can only see the connected account name.
• Audit logging -- Every connection, disconnection, and credential refresh is logged in the workspace audit trail.

For more on Buildorado's security practices, see the security section on the main website.

Coming Soon

The following integrations are on the Buildorado roadmap and will be available in upcoming releases:

Currently in development (manifests exist):

• Salesforce -- Create leads, contacts, and opportunities
• HubSpot -- Create and update contacts and deals
• Jira -- Create and manage issues
• Discord -- Send messages via webhooks
• Telegram -- Send messages via Bot API
• WhatsApp -- Send messages via Business API
• Notion -- Create pages and query databases
• Airtable -- Create and manage records
• Dropbox -- Upload and manage files

Planned (no manifest yet):

• Mailchimp -- Add subscribers to lists and trigger email campaigns
• Zendesk -- Create and update support tickets
• Intercom -- Create conversations and update user profiles
• Shopify -- Create orders and manage inventory
• QuickBooks -- Create invoices and record payments
• GitHub -- Create issues and pull requests from form submissions
• Linear -- Create and assign issues
• Asana -- Create tasks and projects
• Monday.com -- Create items in boards

If you need an integration that is not listed here, you can use webhooks or the HTTP Request node to connect to any service with a REST API. You can also contact the Buildorado team to request a new integration.

Frequently Asked Questions

Can I connect multiple accounts for the same service?

Yes. You can connect as many accounts as you need for any integration. For example, you might connect two different Slack workspaces or multiple Google accounts. When configuring an action node in your workflow, you select which connected account to use from a dropdown menu.

What happens if my integration credentials expire?

Buildorado automatically refreshes OAuth tokens before they expire. If the refresh fails -- for instance, because the account password changed or you revoked access from the third-party service -- the integration status changes to Expired on the Settings page. Workflows using that integration will fail at the action node with a clear error message. To fix it, click Reconnect on the integration settings page and re-authorize.

Are my credentials shared across workspace members?

Connections belong to the workspace, not to individual users. Any workspace member with the Editor or Admin role can use connected integrations in their workflows. Only Admin users can connect or disconnect integrations. This means you connect once and every team member can build workflows with that integration.

Can I use integrations in test mode without affecting production data?

Yes, for services that support test modes. The Stripe integration supports both test and live mode -- you can connect a Stripe test account for development and switch to your live account when publishing. For other integrations, we recommend connecting a sandbox or development account during testing. Buildorado's Preview mode runs the workflow end-to-end, so all action nodes fire, including integrations.