Automation Creates a Contact but Not an Opportunity: What to Check

Why contact and opportunity creation are separate

In most CRM automation platforms, creating a contact and creating an opportunity are two distinct actions. A workflow can create the contact successfully and then fail to create the opportunity because the second action has its own conditions, required fields and pipeline configuration. The contact exists, which tells you the trigger and the data are working. The missing opportunity tells you the problem is in the opportunity creation step specifically.

What to check first

Did a condition skip the opportunity step

Many workflows place the opportunity creation behind a condition. The contact is created unconditionally, but the opportunity is only created if a field matches a value, a tag is present or a lead source qualifies. If the condition was not met, the workflow created the contact and then skipped the opportunity step. Review the branch logic between the contact creation and the opportunity creation. A condition that looks correct can still fail on edge cases like empty values or unexpected lead sources.

Pipeline and stage configuration

The opportunity action selects a pipeline and a stage. If that pipeline was deleted, renamed or replaced, the action may fail silently or skip the creation. Some platforms error when the configured pipeline no longer exists. Confirm the pipeline and stage referenced in the action are still valid and active. A workflow built against an old pipeline structure will keep failing until the action is updated to a current pipeline.

Required fields on the opportunity

Opportunities often have required fields that contacts do not. An opportunity action that lacks a required field value will fail even though the contact creation succeeded. Check the required fields on the opportunity action and confirm the source data fills each one. A missing opportunity name, value or owner field can block the creation. If the source data does not provide a required value, the action needs a default or the form needs to capture the field.

Duplicate prevention logic

Some workflows check for an existing opportunity before creating a new one. If the logic finds an existing opportunity, it may skip the creation to avoid duplicates. This is useful when it works, but it can block legitimate new opportunities when the matching is too broad. A match on contact alone, without checking pipeline or stage, can prevent a new opportunity for a returning lead. Review the duplicate check logic and confirm it matches on the right fields. Duplicate opportunity problems are covered in the guide on automation creating duplicate opportunities.

Multiple workflows and conflicting logic

If more than one workflow handles new contacts, one may create the contact while another is responsible for the opportunity. If the second workflow did not fire or failed, the contact exists without an opportunity. Map out every workflow that runs on new form submissions and confirm which one owns opportunity creation. Overlapping workflows are a common source of partial results and are covered in the guide on too many automation workflows conflicts.

How to test it

1. 1.Submit a test form and confirm the contact is created.
2. 2.Open the workflow history and find the opportunity creation step.
3. 3.If the step was skipped, review the condition that controls it.
4. 4.If the step errored, check the required fields and pipeline configuration.
5. 5.Fix the condition, field or pipeline and resubmit.
6. 6.Confirm the opportunity is now created in the correct pipeline and stage.