# Review an export and release it row by row.

Bring contacts from your existing stack into a shared review list. Your team sees findings and CRM matches and releases single rows for handoff – to the CRM of your choice, HubSpot in the example.

https://listplus.ai/en/gtm-workflows/review-an-export-before-your-crm

## Inputs and connections

Selected rows from your workflow, for example as a CSV. Keep a source reference and your matching fields.

You provide the export. For an agent the list needs the right permissions. CRM connection, field mapping and pipeline are set up once in ListPlus.

## Steps

1. **Open the export in a review list** (Your team · manual in ListPlus). Export the rows from your workflow. Import them into ListPlus or have your agent create the list and add the records.
2. **Hold rows that need a decision** (ListPlus · runs automatically). Conflicting fields, duplicates and CRM matches are flagged. New people, existing records and cases for your team stand apart.
3. **Release row by row** (Your team · manual in ListPlus). Select the reviewed row for the allowed pipeline. Manual release waits for a person. Verify in the CRM that the change arrived.

## Expected sample result

Mia can be released. Ava matches the CRM. Noah's name conflicts with his email. Check delivery of the released row in the CRM separately.

## Costs and boundaries

Standard checks and list operations cost 0 credits. External sources and the configured pipeline destination may have their own charges. The demo sends no data.

The demo shows a supplied export and a manual release. Releasing in ListPlus and confirmed delivery in the CRM are two states.

## Agent prompt

Use my export from Clay. Work in my shared review list, run check_list and inspect the configured CRM match. Show new, existing and ambiguous contacts. Hand off only my selected record IDs to the existing CRM pipeline. Report separately what is waiting for approval and what is confirmed in the CRM.

## Tools

`describe_list`, `add_records`, `check_list`, `query_records`, `send_to_pipeline`

MCP: https://listplus.ai/mcp
REST: https://listplus.ai/a/v1/{action}
API: https://listplus.ai/a

## Sample calls

These calls use fictional IDs. Use the IDs returned by your workspace.

```text
describe_list({ list_id: "<shared_list_id>" })
check_list({ list_id: "<shared_list_id>" })
send_to_pipeline({ list_id: "<shared_list_id>", record_ids: ["<approved_record_id>"], pipeline: "<allowed_pipeline>" })
```