# Teable + DigiParser | Create Records from Document Data

Source: https://www.digiparser.com/integrations/teable

[<- All integrations](/integrations)

![Teable logo](/img/icons/teable.webp) Teable Cloud integration

# Make document data  
part of your Teable base.

Create Teable records from document fields or extracted table rows. Add separate exports when different teams need different tables, mappings, or conditions.

[Start free ↗](https://app.digiparser.com/auth/join)[Setup documentation ->](/docs/guides/integrations/exporting-to-teable)

## Keep the order reference on every line.

Export ordered items as Teable records, with the document-level PO reference alongside each row. Your team can trace individual items back to their order.

1.  1Select the Teable destination table.
2.  2Map item fields and the document-level order reference.
3.  3Export each extracted table row as a record.

![](/_next/image?url=%2Fimages%2Fintegrations%2Fteable-workflow-v1.webp&w=3840&q=75&dpl=dpl_4CEHPWQCJofunboV6oYnMCcudHh5)

## One parser. More than one destination.

Example - AP summary export

1.  01Processed supplier invoice
2.  02One record per document
3.  03Teable: Invoice register

Example - detailed line export

1.  01Extracted invoice table
2.  02One record per table row
3.  03Teable: Invoice lines

Use **Add another** to configure another Teable export. Each destination has its own account, table, record mode, mappings, and conditions.

## Connect with OAuth, then choose an existing table

1.  01
    
    ### Add the Teable export
    
    Open the parser's Integrations page, add Teable, and expand the export.
    
2.  02
    
    ### Connect Teable Cloud
    
    Click Connect Teable account, sign in, review permissions, and approve. No personal access token is needed.
    
3.  03
    
    ### Select account, base, and table
    
    DigiParser loads the destinations available to the connected account. It does not create or change the table structure.
    
4.  04
    
    ### Select record mode and map fields
    
    Choose one record per document or per extracted table row. Map writable fields; document fields can repeat on table-row records.
    
5.  05
    
    ### Save and add conditions if needed
    
    Save Teable export. Use Add conditions to run if only selected documents should reach this destination.
    
6.  06
    
    ### Check a sample record
    
    Process a document and verify the destination values and record count. Inspect required fields and their expected types if creation fails.
    

## Conditions select documents, not individual table rows

### Example - an AP exception table

Set a document-level condition on a parser field used by your workflow. Matching documents run this export with its saved record mode and mappings.

If the export is in table-row mode, the condition applies to the complete export. It does not filter individual extracted lines.

## Give every record a useful source reference

Values available for Teable mapping

Source

Use

Parser fields

Invoice reference, customer code, amount or date

Selected table columns

One record for each extracted line

Document name and link

Trace a record back to its source

Markdown URL and creation date

Preserve document context where useful

Computed and attachment fields cannot be mapped. Unmapped values are not sent. Refresh the destination after changing its table fields.

## Retries account for completed writes

DigiParser records Teable writes so a normal workflow retry does not create the same record again. Failed writes can retry. If the result of a write is uncertain, DigiParser does not automatically repeat it and risk a duplicate.

For a missing base or table, check account access and refresh the destination. If authorization expires, reconnect Teable.

[Start free ↗](https://app.digiparser.com/auth/join)[Setup documentation ->](/docs/guides/integrations/exporting-to-teable)