Validate Incoming CSV Files Before CRM Enrichment

2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

/deepline-gtm Validate this CSV before Deepline enrichment. Parse quoted commas and embedded newlines correctly. Preserve source row identity. Separate file-level failures from row-level missing fields, invalid formats, and duplicates. Return accepted rows plus a rejection report with reasons. Do not start enrichment or repair the CRM while input requirements remain unresolved.

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

3. Review the result

The accepted and rejected records reconcile to the parsed file. An email format check is not mailbox verification, and physical line counts are not necessarily record counts.

Ask your agent:

/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.

Approve a larger job, recurring work, or external changes only after reviewing that decision.

No. File structure and row acceptance are separate checks. Preserve row-level exceptions and their source identities.

How-to guides

Validate Incoming CSV Files Before CRM Enrichment

1. Have your context ready

2. Ask your agent

3. Review the result

Check your understanding

​1. Have your context ready

​2. Ask your agent

​3. Review the result

​Check your understanding

​Related guides

1. Have your context ready

2. Ask your agent

3. Review the result

Check your understanding

Related guides