# Find a CRM contact before creating a duplicate

Start a deliberate CRM contact lookup with a test email and inspect the result before adding any write action.

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## The business outcome

Start a deliberate CRM contact lookup with a test email and inspect the result before adding any write action.

This is an importable starter using Chatigram’s current native nodes. It needs destination-specific setup; it does not imply a dedicated connector for every CRM or ERP brand. Check your software’s API documentation and permissions.

## Before you begin

Replace the placeholder API URL, authorization, test email, and the query parameter required by your CRM. This starter performs no create action.

The reserved example.invalid endpoint is deliberately non-working. No real customer data, account credentials, or private resource identifiers are embedded. Keep the workflow disabled until setup is complete.

## Configure the workflow

1. Choose a controlled test email and configure contactLookup for the CRM search endpoint.
2. Review whether the API performs an exact email match, a broad search, or a paginated result.
3. Inspect contactResult before adding any create or update node. An empty list, access error, and partial search result are different outcomes.
4. If you extend the pattern to create a contact, use the CRM’s stable identifier or duplicate-prevention support.

## Test the outcomes

- Test one known contact and one known non-match.
- Check pagination if the CRM can return several matches.
- Confirm an API failure never falls through into an automatic create action.

Open [Workflow Activity](/workflows/activity/) after the test. Import validation checks the definition; it does not prove a remote API accepted the business operation. Check the destination before repeating a send or write.

## Make it your own

Put reusable public settings in [Properties](/workflows/properties/), configure credentials through the protected connection options, and keep explicit error paths. Explore [App Connections](/integrations/overview/) for existing provider-specific actions you can substitute through the editor.

Use the copy controls below for the complete workflow or its first node. The diagram and downloads come from the same definition. Use Share recipe to share the guide’s public address.


## Copyable workflow

https://docs.chatigram.com/examples/crm-contact-lookup.json