Skip to content
Learn › Share and export: open the docs menu

Set up a Mammoth export and pick a destination

Depends on the destination: see Export destinations by plan · Updated 8 Nov 2026

An export delivers a View's data to a destination every time the pipeline runs: a database or warehouse, a file store, an app, an API or another dataset. Click Export in the View toolbar, pick a destination and click Apply. The export becomes a task pinned to the end of your pipeline; which destinations you can use depends on your plan.

Set up an export

  1. In the View toolbar, click Export. The Export menu, titled with the View's name, opens on the External Destinations tab.
  2. Pick a destination card, or switch to the Mammoth Managed tab for Send to Dataset, Live link or a managed database.
  3. Fill in the export form in the pipeline panel. A summary row with a pencil icon lets you switch to another category or connector.
  4. Click Apply. The export runs straight away and after every pipeline run.
TabWho manages itUse when
External DestinationsYou provide credentials or connect an accountYou have your own database, warehouse, server or app
Mammoth ManagedMammoth provisions everythingYou want zero infrastructure setup
Export menu, Mammoth Managed tab, with the Send to Dataset, Live link, Google BigQuery and PostgreSQL cards

Export menu open on External Destinations: Azure Blob Storage, Google BigQuery, Databricks, Elasticsearch, Email, REST API Export, Google Sheets, SQL Server, MySQL, OneDrive, PostgreSQL, Amazon Redshift, SFTP, SharePoint, Snowflake and Tableau Server/Cloud

Which export destination to use

SituationBest option
Colleagues need the file in their inbox after each updateExport → Email
A team works from a shared spreadsheetExport → Google Sheets (Export to files and apps)
Data belongs in your warehouseExport → Snowflake, Databricks or another database (Send data to a database or warehouse)
A BI tool needs to query Mammoth data via URLExport → Live link
Tableau or Power BI needs automatic data deliveryExport → a managed or external database, or Tableau Server/Cloud
Push results into another Mammoth DatasetExport → Send to Dataset
An API Mammoth has no card forExport → REST API Export or Somewhere else… (Export to an API)
A destination must get data at fixed times, even when nothing changedExport, then an Export on a schedule automation
An email should go out at most once a day or weekExport → Email, with Send at most
Someone needs the data onceNot an export: download a copy

Export destinations by plan

A card shows a Trial pill when your plan doesn't include that destination. Hover the pill to see which plans include it ("Included in" and the plan names). Clicking a gated card opens the upgrade prompt instead of the form.

DestinationPlan
Send to Dataset, Snowflake, Databricks, Google Sheets, EmailEvery plan, no Trial pill
PostgreSQL, MySQL, SQL Server, Amazon Redshift, Google BigQuery, ElasticsearchPaid plans (database exports)
SFTP, SharePoint, OneDrive, Azure Blob StoragePaid plans (file exports)
Live link, Tableau Server/Cloud, REST API ExportTeam and Pro
Mammoth-managed Google BigQuery and PostgreSQLPro
Somewhere else… (AI custom destination)Available on Enterprise plans (it opens the AI Agent)

A workspace that is over its managed-database limit gets an error when it creates a managed table.

Task position and update method

The form footer shows a read-only Task Position line and, where the destination has one, an Update Method line. Click the pencil icon to edit them.

Keep the export at the end of the pipeline

By default the export task sits at the end of the pipeline, so it runs after all transformation tasks, and Mammoth keeps it there. Change it only if you need a specific position (rare). Live link and the managed databases have no position option.

Choose how data is written: Replace, Combine or Merge

MethodBehaviour
ReplaceReplaces the table's data on each run
CombineAdds new rows to the existing table without changing existing rows
MergeUpdates rows that match the Reference Column values and inserts rows with no match

With Merge, choose at least one Reference Column: a column whose values uniquely identify each row, like a primary key. Where you set the method depends on the destination:

DestinationWhere you set it
Send to DatasetIn the form, under Each time this runs
Google BigQuery, PostgreSQL, MySQL, SQL Server, Amazon Redshift, Snowflake and Databricks (external)Replace, Combine or Merge as the Update method
Google SheetsReplace or Append, as the form's Write mode

Send only new rows on each run

The Send only new rows checkbox, below When it runs, makes each run send only rows added since the last run.

  1. Tick Send only new rows.
  2. Under Using the column, pick a date or number column whose values only grow, such as an ID or a created date. Date columns are listed first, and the first one is preselected.
  3. Click Apply. The next run sends every row; later runs send only rows with a larger value than any already sent.

After a run, the form says which value the next run starts after. Click Start over and send every row next time to reset it. Picking a different column also starts over.

DestinationCan send only new rows
PostgreSQL, MySQL, SQL Server, Amazon Redshift, Google BigQuery, Snowflake, DatabricksWith Combine or Merge. With Replace: "Choose Combine or Merge to send only new rows. Replace would leave just the newest rows in the table."
Google SheetsWith Append only
Email, REST API ExportYes
SFTP, SharePoint, OneDrive, Azure Blob Storage, Elasticsearch, Tableau Server/CloudNo: "This destination is replaced on every run, so it can't send only new rows."

If the View has no date or number column, the form says "Sending only new rows needs a number or date column whose values only grow, like an ID or a created date."

Was this page helpful?

Something wrong? support@mammoth.io