I have a Zap with the following setup:
- Trigger: Webhooks by Zapier (Catch Hook) — receives a JSON payload from an external service
- Action: Commusoft — Create New Job
When the Zap runs, the "Create New Job" action returns a 200 response, so at first glance it appears to succeed. However, no job is ever created in Commusoft.
Root cause I've identified
Looking at the request details in the Zap run history, the action is posting to:
POST https://api-zapier.commusoft.us/webhooks
The response is:
{
"id": 166,
"message": "zapier subscription successfully done!",
"statusCode": 200
}
The /webhooks endpoint on Commusoft's API is their REST Hooks subscription endpoint — it registers Zapier to receive events from Commusoft. It is not the job creation endpoint. Every time the Zap runs, it is simply re-registering a webhook subscription and returning a fake success, without ever creating a job.
This appears to be a bug in the Commusoft Zapier integration itself — the "Create New Job" action is internally wired to the wrong API endpoint.
What I need help with
- Is this a known issue with the Commusoft Zapier integration?
- Has anyone successfully used Commusoft's "Create New Job" action and had it actually create jobs? If so, what setup worked for you?
- As a workaround, I'm considering replacing the Commusoft action with Webhooks by Zapier → POST and calling Commusoft's REST API directly. Does anyone know what the correct Commusoft API endpoint is for job creation, and what fields it expects?
Environment
- Commusoft region: US (
api-zapier.commusoft.us) - Zapier Zap ID: XXXXXXXXX
Any help appreciated — happy to provide more details.
This post has been edited by a moderator to remove a Zap ID. Please remember that this is a public forum and avoid sharing personal or potentially sensitive details.
