For the complete documentation index, see llms.txt. This page is also available as Markdown.

Exporting an email to an External File Gateway

To export a version to your External File Gateway you will need to select the Project, Mailing and finally the Version you would like to export. You can export from the Mailing level, Version level or from the visual editor. To export:

  1. In Taxi, head to your Home screen Select the Project that contains the version you want to export.

  2. Select the Mailing If you are Admin you can select the Kebab menu and select 'Export' on the mailing level.

  3. After selecting the Mailing you will see the Versions page Select the 'Export Mailing' option on the right-hand side of the screen under the Exports section. Alternatively select the version you want to export to open it in the visual editor.

  4. In the visual editor, select 'Export Mailing'

  5. On the Export page, scroll to ESP connectors Select your External File Gateway connector.

  6. Under the Segmentation section You can select if you want to export one version or use a segment set. Each version you export will result in a separate JSON file written to your SFTP host.

  7. Click 'Start Export' You will see a green banner when your export is complete. The connector writes one JSON file per version to your configured SFTP host using the filename pattern set up on the connector.

What the exported JSON looks like

Each file follows this shape (the exact contents of data and metadata depend on the field names configured on the connector — see Setting up the External File Gateway connector):

  {
    "campaign_name": "My Newsletter: v1",
    "uploaded_by": "user@example.com",
    "updated_at": "2026-05-05T15:00:00Z",
    "project_url": "https://your-org.emailcms.net/versions/123",
    "data": {
      "campaign_html": "<html>…</html>",
      "campaign_plaintext": "",
      "subject": "Your subject line",
      "<data_field_name>": "<resolved value>",
      "global_content": {
        "<key field value>": "<value field value>"
      }
    },
    "metadata": {
      "<metadata_field_name>": "<resolved value>"
    }
  }

Last updated