# Connect identification to a customer-defined workflow

Use case · Platforms · Planned API workflow

Canonical page: https://datasdk.ai/use-cases/connect-identification-to-a-customer-defined-workflow

Plan explicit user control over research and review steps.

## Who this helps

A platform wants users to choose what happens after a company match.

## How to use it

1. Define supported actions and require an authorized owner.
2. Show the company evidence before consequential actions.
3. Agree the API contract and validate the workflow with sample data.

## Illustrative example

A proposed rule would queue a record for review rather than automatically email a guessed contact.

## What to check

The API is coming soon, and workflow automation must be built and authorized separately.

## How Data SDK fits

The full Data SDK API is coming soon. Platform and AI-agent workflows are planning examples. Confirm access, data delivery, usage, branding, and resale terms before building or selling a feature.

These are suggested workflows, not a list of built-in integrations. Use your own approved analytics, CRM, and research process where needed. Matches and fields vary. A company match does not identify a person or prove buying intent.

## Related reading

- [Sales handoff](https://datasdk.ai/glossary/sales-handoff): A sales handoff passes an account or opportunity between people or teams.
- [API](https://datasdk.ai/glossary/api): An application programming interface lets software request data or actions from other software.
- [Human review](https://datasdk.ai/glossary/human-review): Human review puts a person in the loop before a result is accepted or acted on.
- [Offer identification in a website-builder product](https://datasdk.ai/use-cases/offer-identification-in-a-website-builder-product): Plan identification as a clearly explained optional website capability.
- [Build a tenant-safe company lookup service](https://datasdk.ai/use-cases/build-a-tenant-safe-company-lookup-service): Plan company lookup around authorized customer contexts.
- [Design a graceful no-match experience](https://datasdk.ai/use-cases/design-a-graceful-no-match-experience): Avoid misleading users with guessed names or stale company cards.

[Glossary](https://datasdk.ai/glossary) · [Use cases](https://datasdk.ai/use-cases) · [Comparisons](https://datasdk.ai/vs) · [For businesses](https://datasdk.ai/for-businesses) · [For builders](https://datasdk.ai/for-builders)