---
title: "Exporting Document Data from Rossum Using Zapier"
slug: "exporting-document-data-from-rossum-using-zapier"
updated: 2025-07-09T08:42:19Z
published: 2025-07-09T08:42:19Z
canonical: "knowledge-base.rossum.ai/exporting-document-data-from-rossum-using-zapier"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge-base.rossum.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Exporting Document Data from Rossum Using Zapier

In this guide, we'll create a Zap, which will run each time document is exported in the Rossum app. By exporting, we mean that a document transitions to "exported" status. Captured data will then be passed to [Airtable](https://zapier.com/apps/airtable/integrations).

Airtable is an application that lets you store and organize your project data. In our case, the "project" is using their ["Order Tracking & Invoicing" template](https://www.airtable.com/templates/order-tracking-and-invoicing/expHekrRJqQgLexBq). But remember, you can choose any Zapier integration app instead.

## Step 1: Create a new Zap

Again, with an [account in Zapier](https://zapier.com/sign-up) go to [Zap editor](https://zapier.com/app/login?next=%2Feditor%2F&redirect_cause=auth-required) and create a new Zap. "Export a Document" is a trigger, which means it'll be the first Zap step. Search for the Rossum app and select it.

## Step 2: Set up a Trigger

In the "Trigger event" input, we'll select "Document Export".

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2001.png)

In the following step, we authenticate the Zap by providing Rossum credentials in a pop-up tab.

Once we're in the "Customize Document" section, we can choose a Rossum queue, in which we want to register export events.

**Export As File** field is a simple boolean. If set to True, a new field of **File Format** will appear. Selecting this option will result in this Zap step having a file of a given format as an output. That can be useful when you want to simply store your captured data.

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2002.png)

However, since Airtable action can accept individual data fields to create a new record, we'll choose False. That way, we'll be able to reference individual datapoints in the Airtable part of this Zap.

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2003.png)

## Step 3: Test the Trigger

Depending on whether you've chosen to export as a file or not, you'll see different outputs of the test call of this trigger.

If you're **exporting as a file**, you'll see something like this. There's a file field yielding "(Exists but not shown)", indicating that there's a raw file data in there. The output also contains some metadata about the annotation you exported. The metadata loosely corresponds to Rossum [Webhooks](https://elis.rossum.ai/api/docs/#webhook-vs-connector).

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2004.png)

Given we set "Export as File" set to **False**, the output will look like this for us. This shape is basically a result of our [export endpoint](https://elis.rossum.ai/api/docs/#export-annotations). You can see individual captured fields and their values. Which is ideal for our use-case.

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2005.png)

## Step 4: Set up the Airtable "Create a Record" action

Again, we choose the app and its action. We want to create a record in Airtable. Following up with successful authentication of Airtable. Airtable authentication requires a token, instead of a username and password. This token can be obtained in account settings in Airtable.

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2006.png)

The customization step is different for every app. Since we're creating an invoice in Airtable, we select base (which we first created in Airtable from "Order Tracking & Invoicing" template), a table and then we map Rossum fields defined in the [Schema](https://elis.rossum.ai/api/docs/#document-schema) to their corresponding fields in the form.

> [!NOTE]
> 📘 Mapping captured fields
> 
> This mapping from our Rossum schema to the Airtable fields of a record is the reason why we made the output of Rossum trigger be raw data instead of a file.

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2007.png)

## Step 5: Test the "Create a Record" action

And as always, the last step is testing. Running the test will actually create a new record in Airtable. You can check that's true in Airtable.

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2008.png)

You can add another action from any app in the next step of this Zap to create even more elaborate pipelines. However, this is where this guide ends.

## Step 6: Victory

And that's it! All we have to do is to turn this Zap on and sit back as the data captured by Rossum fills your Airtables.

![](https://cdn.document360.io/1bb6f6bc-c04c-4ace-a1e8-8c4cfd3fbc98/Images/Documentation/Devs%20-%20Exporting%20Document%20Data%20from%20Rossum%20Using%20Zapier%2009.png)

> [!NOTE]
> 📘 Rossum triggers are Instant
> 
> Unlike many other apps, Rossum triggers in Zapier are "Instant". That means there will be no delay between the document export in Rossum, and this Zap running in its entirety.