Destinations

Destinations register the external analytics targets the suite writes to — a data warehouse, object storage bucket or BI connector. Each record holds the connection type, endpoint and credentials. Configuring destinations correctly is what lets pipelines deliver data securely to the right downstream system.

Workflow

Open Destinations from the Data Warehouse export menu.
Create a destination and pick the connector type.
Enter the endpoint, database/bucket and credentials.
Test the connection.
Activate so pipelines can target it.

Fields reference

Every field on this screen, drawn from the live data model.

Field	Type	Required	Description
Code `code`	Text	Yes	Unique short code, used in audit logs.
Website Messages `website_message_ids`	List	—	Website communication history
Base URL / Endpoint `base_url`	Text	—	Optional. For HTTP POST or self-hosted Snowflake/Redshift endpoints.
Name `name`	Text	Yes	Name
Provider `provider`	Choice: Google BigQuery, Snowflake, Amazon Redshift, Amazon S3 (Parquet), SFTP (CSV gzip), Generic HTTP POST	Yes	Provider
Has Message `has_message`	Yes/No	—	Has Message
Ratings `rating_ids`	List	—	Ratings
Sequence `sequence`	Number	—	Sequence
Credentials (encrypted) `credentials_enc`	Long text	—	Credentials (encrypted)
Provider Config (JSON) `config_json`	Long text	—	Provider Config (JSON)
Active `active`	Yes/No	—	Active
Company `company_id`	Link → res.company	—	Company
Pipelines `pipeline_ids`	List	—	Pipelines
Pipeline Count `pipeline_count`	Number	—	Pipeline Count

Actions & buttons

Buttons available on this screen and what they do:

Test Connection

Notes & rules

Model mfi.dw.destination; the external warehouse/BI target master.
Holds connector type, endpoint and authentication credentials.
Common targets: SQL warehouse, object storage, BI connector.
Referenced by pipelines as their write target.

Technical model: mfi.dw.destination · Record: Data Warehouse Destination