Ingest and sync data from any source application to a Postgres data warehouse.
Connect any of your business applications to a Postgres-compatible data warehouse. Flows360 provides a native, secure connector for Postgres to act as a destination for your data integration workflows. This enables you to consolidate 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 is straightforward, requiring 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. Automate data pipelines from CRM, ERP, and marketing automation platforms without writing custom code. This allows your data and analytics teams to focus on generating insights rather than managing brittle ETL scripts.
Common use cases
- Centralized Data Warehousing: Consolidate data from multiple cloud applications into a single Postgres database for a unified view of business operations.
- Business Intelligence and Analytics: Feed clean, structured data into your BI tools by connecting them to your Postgres warehouse, populated with up-to-date information from your source systems.
- Data Archiving: Automatically archive historical data from operational systems like CRMs or support desks into a cost-effective Postgres instance for compliance and long-term storage.
- Operational Reporting: Build custom reports and dashboards using data replicated from various departments into Postgres, enabling cross-functional insights.
Sync scenarios
- Sync Salesforce Accounts and Contacts to Postgres tables.
- Replicate HubSpot Deals and Companies into a Postgres database.
- Archive Zendesk Tickets in a centralized Postgres data warehouse.
- Consolidate Stripe payment and subscription data in Postgres for analysis.
Frequently asked questions
What types of Postgres databases are supported?
The Flows360 Postgres connector works with any standard, network-accessible Postgres database. This includes self-hosted instances and managed services like Amazon RDS for PostgreSQL, Neon, and Supabase.
Is this connector a source or a destination?
The Postgres connector is a destination. It allows you to write data from your source applications into your Postgres database tables.
How does Flows360 connect to my private Postgres database?
For databases not publicly accessible, you will need to allowlist Flows360's static IP addresses in your firewall rules to permit a secure connection. Your database credentials are encrypted and stored securely.
Do I need to create tables in Postgres before syncing?
Yes, you must define the target schema and tables in your Postgres database before running a sync. Flows360 will map source data fields to the corresponding columns in your specified tables.
- Auth method: Username/Password
- Required scopes: 1
- Supported objects: 1
- Supported actions: 1
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.
Setup steps
1. Create a Dedicated Database User
For security and auditing purposes, create a dedicated user for Flows360 in your Postgres database.
“`sql
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.
“`sql
— 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`).
Required scopes
]
Supported objects
- Table
Supported actions
- 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.
Use cases
- Customer 360
- Product Analytics
- Revenue Operations
- Data Warehousing
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.