404 and Record not found error

Hi ​@ggkkmanila 

For us to have true context about what you are referring to post screenshot showing how your Zap steps are outlined/configured along with the encountered error.

https://cdn.zappy.app/dd889de776f49aedce7d6036f45168cc.png

​@ggkkmanila 

Screenshot is a bit blurry and does not show how the Zap steps with errors are configured in the CONFIGURE tab while in EDIT mode.

Hi ​@ggkkmanila 

Have you tried using LeadConnector's API directly via Zapier's Webhook action instead of the built-in LeadConnector integration? That usually does the trick with 404 errors—sometimes the pre-built actions have limitations or outdated endpoints, but hitting the API directly gives you more control and visibility into what's being sent.

Here's the LeadConnector API documentation that might help: https://marketplace.gohighlevel.com/docs/ghl/opportunities/update-opportunity

This shows exactly what endpoints Zapier is calling and the expected data structure for the Add/Update Opportunity action.

If you're still running into issues, could you share a clear screenshot of:

1. The failed Zap run showing the full 404 error

2. How your Add/Update Opportunity step is configured (with sensitive info blurred)

3. The data from your database sheet step that's feeding into LeadConnector

Sometimes the issue is in how fields are mapped or formatted. A clear look at your setup would help spot what might be going wrong!

And if you'd rather just get it sorted quickly, I offer a free 20-min Zapier troubleshooting call. Book it under Resources on my Zapier Directory profile: https://zapier.com/partnerdirectory/automatemybiz!-->

!-->

Usually this means the webhook is getting the data fine, but one of the next steps is using the wrong ID or trying to update the record too early.

So even if the data looks correct in the webhook, the other app can still say 404 / record not found.

Most common reasons:

• the step is using the wrong type of ID

• the record is not fully created yet when the next step runs

• the record is in a different account/location

• there’s a small formatting issue in the value

I’d check this:

• make sure each step is using the correct ID

• add a short delay before the update step

• test the step with a real run, not just the mapped fields

• if possible, use a find/search step first, then use the ID from that step

So the webhook is probably not the problem it’s usually the ID or timing in the later action steps.