Skip to main content
Question

Simpro integration returning "Invalid route" error on multiple actions/triggers

  • June 29, 2026
  • 1 reply
  • 3 views

I'm trying to set up a Zap called "Simpro Completed Jobs to Google Sheets Log" using the Simpro (simPROCLIAPI) integration, and I'm hitting an "Invalid route" error in two separate places, which suggests a problem with the Simpro integration itself rather than my configuration.

Issue 1: Trigger activation failure
- Zap: Simpro Completed Jobs to Google Sheets Log
- Step: "Job Updated" trigger (Simpro)
- Error when turning the Zap on: "Your Zap could not be turned on... The app returned 'Invalid route.'"
- The Zap was subsequently auto-disabled with the message "Zap turned off due to a partner issue."

Issue 2: Action call failure
- Same Simpro connection
- Action: "Find Schedule" (find_schedule)
- Called with params: Date = 2026-06-29, Type = job
- Error returned: "Error during execution: The app returned 'Invalid route.'"

Both errors point to the same underlying issue with how the Simpro integration is routing certain API calls. Other Simpro actions (e.g. "Find Job") work fine, so this seems isolated to specific endpoints (Job Updated trigger, Find Schedule action).

Could you please investigate whether there's a known issue with these specific Simpro endpoints, and let me know what's needed to get the "Job Updated" trigger working so my Zap can run as intended?

Thanks,
Darrin

1 reply

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • June 29, 2026

Hi ​@DarrinS, welcome to the Community! 😁

I did some checking on those “Invalid route” errors and they’re usually due to an issue with the Company ID that was entered when connecting the account. The ID needs to be 0 for single company simPRO environments, but if you’re using multi-company then you’d need to use the ID stated in your simPRO account (under System > Setup > Company).

Can you check the Company ID and try adding a brand new app connection to Simpro? Once that’s done, select that new connection in any Zap that’s running into those errors and then replay the errored Zap runs to see if that sorts it.

Let us know whether that fixes it! 🤞