Grin to Apache Iceberg integration

Connect Grin to Apache Iceberg and automatically sync your marketing platform data. Weld extracts data from Grin, loads it into Apache Iceberg, and lets you transform the data using SQL or dbt, no custom scripts required.

4.8 on G2
GrinSource
WeldWeld
Apache IcebergWarehouse
Weld · New sync
GrinSourceGrinConnected
Tables to sync
  • contact32 cols
  • campaign27 cols
  • activation18 cols
  • media_library_content59 cols
  • proposal24 cols
  • partnership33 cols
  • Extract
  • Load
  • Keep in sync
Apache IcebergDestinationApache IcebergReady
grin schema
  • grin.contactSynced
  • grin.campaignSyncing
  • grin.activationSynced
  • grin.media_library_contentSynced
  • grin.proposalSynced
  • grin.partnershipSynced
Grin tables
66
fields, typed
925
relationships kept
94
agent context included
MCP

Trusted by data and AI teams

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up Grin to Apache Iceberg in Weld.
In the app, with the API or an agent.

Weld · New Grin sync
GrinNew connectionGrinAuthorised
Connection namegrin
AuthorizeOpens Grin to grant read access
Use cases

Why sync Grin to Apache Iceberg?
Ready for analysis.

Centralizing your Grin data in Apache Iceberg lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying Grin data directly in Apache Iceberg using SQL or your preferred BI tool.

  • Centralized data warehouse

    Bring Grin data into Apache Iceberg alongside other sources to create a single source of truth for your organization.

  • Automated reporting

    Replace manual exports and spreadsheet-based reporting with automated pipelines from Grin to Apache Iceberg. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every Grin table, keys intact.

Weld syncs the objects the Grin connector exposes into Apache Iceberg, and you choose which tables and fields to include. The connector's docs list what is available.

Open the schema explorer
All 66 tables
  • contact
  • campaign
  • activation
  • media_library_content
  • proposal
  • partnership
  • conversion
  • affiliate_link
  • campaign_conversion
  • partnership_job
  • content
  • proposal_deliverable
  • campaign_content
  • proposal_deliverable_content
  • discount_code_group
  • contact_address
  • contact_payment
  • contact_order
  • discount_code
  • product_selection
  • contact_campaign
  • partnership_proposal
  • activation_brief
  • campaign_payable
  • task
  • activation_member
  • ecommerce_account
  • payable
  • proposal_file
  • contact_custom_property_value
  • and 33 more
Weld MCP server

Ask your agent.
It queries Apache Iceberg for you.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Grin context, finds the tables it needs and runs the query in Apache Iceberg.

Claude CodeOpus 5
>

How many campaign rows do we have per discount_code_group? Use our Grin data in Apache Iceberg.

Reading the Grin context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.grin.campaign
raw.grin.discount_code_group
+ 64 more Grin tables
●weld·get_reference_schema
⎿campaign · 27 columns
joins discount_code_group on discount_code_group_id
●weld·run_query
⎿select d.id, count(*) from {{raw.grin.campaign}} c
join {{raw.grin.discount_code_group}} d on c.discount_code_group_id = d.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Grin data in Apache Iceberg
>Ask about your Grin data
Under the hood

Technical considerations.
What to expect.

Incremental syncing
Weld uses incremental syncing where supported by the Grin API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If Grin adds new fields, they're detected and added to the corresponding Apache Iceberg tables.
Data freshness
Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
Security
All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
FAQ

Common questions.
About Grin to Apache Iceberg.

Start syncing Grin to Apache Iceberg.

Set up your Grin data pipeline in minutes. No credit card required. Free for 14 days.

GrinSource
WeldWeld
Apache IcebergWarehouse