Overview
Connect your business applications to a Postgres-compatible data warehouse. Flows360 provides a native, secure connector for Postgres to act as a destination for data integration workflows. This enables the consolidation of data from multiple sources for analytics, reporting, or operational use.
The connector is compatible with any standard Postgres database, including managed services like Amazon RDS, Neon, and Supabase, as well as self-hosted instances. Configuration requires only your database credentials and network access for the Flows360 platform.
By using Flows360 to populate your Postgres warehouse, you can build a single source of truth for your business data. This allows data and analytics teams to focus on generating insights rather than managing brittle ETL scripts. The connector dynamically manages schema changes, creating and altering tables as needed based on the source data structure.
Capability summary
Authentication
Auth method: Username/Password
Required scopes
]
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Table | No | Yes | Flows360 dynamically creates and manages tables in the destination schema based on the source object's structure and the workflow configuration. There are no pre-defined objects. |
Supported actions
| Action | Description |
|---|---|
| Sync Records | Writes records from a source application to a specified table in the Postgres database. This action will create the table and columns if they do not exist and alter them as needed on subsequent syncs. |
Setup steps
1. Create a Dedicated Database User
For security and auditing purposes, create a dedicated user for Flows360 in your Postgres database.
CREATE USER flows360_user WITH PASSWORD 'your-strong-password';2. Grant Permissions
The user requires permissions to connect to the database, create and use a schema, and manage tables within that schema.
-- Grant connect access to the database
GRANT CONNECT ON DATABASE your_database TO flows360_user;
-- Create a schema for Flows360 to manage its tables
CREATE SCHEMA flows360_schema;
-- Grant usage on the schema
GRANT USAGE, CREATE ON SCHEMA flows360_schema TO flows360_user;
-- Grant all permissions on tables within the schema
-- This allows Flows360 to create, read, update, and delete table data
ALTER DEFAULT PRIVILEGES IN SCHEMA flows360_schema GRANT ALL ON TABLES TO flows360_user;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA flows360_schema TO flows360_user;3. Ensure Network Accessibility
Your Postgres database must be publicly accessible from Flows360's static IP addresses. You may need to add these IPs to your firewall's allowlist or your cloud provider's security group rules (e.g., Amazon RDS Security Groups). Refer to Flows360 documentation for the current list of egress IPs.
4. Configure the Connector
In the Flows360 connection setup, provide the following details:
- Host: The hostname or IP address of your database server.
- Port: The port your database is listening on (default is 5432).
- Database: The name of the database to connect to.
- Username: The user created in Step 1 (e.g.,
flows360_user). - Password: The password for the dedicated user.
- Schema: The schema for Flows360 to use (e.g.,
flows360_schema).
Limitations
- This connector is a destination-only connector. It can only write data to Postgres.
- The user is responsible for ensuring network accessibility. The database must be accessible from Flows360's egress IP addresses, which may require configuring firewall rules.
- Sync performance is dependent on the provisioned resources and configuration of the target database instance.
- Flows360 will attempt to map data types from the source system to appropriate Postgres data types. Exotic or custom data types may not be mapped correctly.
- The connector requires permissions to create and alter tables within the specified schema. It is not suitable for write-only roles with a fixed, pre-defined schema.