Agendor to Yellowfin Integration
AI-first ETL from Agendor into Yellowfin. Governed entities, incremental sync, typed landing tables.
How Datrise loads Agendor into Yellowfin
Datrise syncs Agendor's organizations, people, deals, funnel stages, activities, and proposals into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.
Ideal for dashboards with automated data storytelling.
Endpoints
Agendor: Brazilian sales CRM for pipeline and account follow-up.
Yellowfin: BI suite with dashboards, automated insights, and data storytelling.
How Agendor entities map to Yellowfin
| Agendor entity | Yellowfin object | Notes |
|---|---|---|
| organizations | agendor_organizations | id PK · custom fields → flattened columns |
| people | agendor_people | id PK · linked to agendor_organizations |
| deals | agendor_deals | id PK · linked to agendor_organizations |
| funnel stages | agendor_funnel_stages | id PK · linked to agendor_organizations |
FAQ
How does Datrise handle Agendor's custom fields in Yellowfin?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Yellowfin types.
How does the Agendor to Yellowfin sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Agendor
Early access
Connect Agendor to Yellowfin the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.