hotglue Docs home page
Search...
⌘K
Ask AI
Status
Dashboard
Dashboard
Search...
Navigation
Flows
V2 Bidirectional Flows
Documentation
API Reference
Unified Schemas
Getting Started
Introduction
FAQ
Key Concepts
Tenants
Jobs
Connectors
Flows
Flows
V1 Source Flows
V1 Target Flows
V2 Bidirectional Flows
Environments
Managed authentication
Embedded Widget
Magic Links
Transformation
Overview
Gluestick
Writing a basic script
Debugging a script
Snapshots
Use Cases
Sample Scripts
Custom Connectors
Taps
Building targets
Unified Schema
Introduction
Accounting Schema
E-Commerce Schema
CRM Schema
Environment Settings
Widget settings
White-label
Job settings
Webhooks
Environment Variables
CLI
Overview
Configuration
Env
ETL
Flows
Jobs
Tenants
Connectors
Core Connectors
Community Connectors
On this page
Bidirectional flow structure
Examples
Flows
V2 Bidirectional Flows
What are bidirectional flows?
If you need to read and write data to the same integration, you can use a bidirectional flow to use the same connection for both.
In a V2 flow, your tenants will link their account once, allowing you to run two types of jobs:
Read jobs — Read data from their linked account
Write jobs — Write data to their linked account
Bidirectional flows utilize the
V2 API
and
V2 Connectors
Bidirectional flow structure
There are 3 types of connectors in a bidirectional flow:
The primary connector which your tenant links to
The target connector to be used in
Read
jobs
The source connector to be used in
Write
jobs
Examples
Common uses of Bidirectional flows include:
Have tenants link their CRM:
Use
Read
jobs to sync their CRM data to your database
Use
Write
jobs to sync custom fields from your platform to their CRM
Have tenants link their own database:
Use
Read
jobs to import their data into your platform via a webhook
Use
Write
jobs to sync updates made on your platform back to their database
V1 Target Flows
Environments
Assistant
Responses are generated using AI and may contain mistakes.