Troubleshooting Webhook Registration Errors and Permission Requirements for Real-Time ServiceNow Integration

·Jul 31, 2026 10:13 PM·

Hi All, I'm converting a working polling action to real-time action to check servicenow for new incidents. I'm now seeing webhook registration errors and cannot get it working. Google sends me to a systematic article that is no longer, explaining new permissions I need for real-time. Anyone have an idea what new permissions I would need and/or specic tables or data conditions? Seems like a long wait to use support for what should be a quick article read. Full error is "Webhook registration error. API returned: Connected user does not have sufficient permission. Make sure the required access control is granted."

5 comments

· Sorted by Oldest

richy.mulcahy
·
·
dkuroda does this help? docs.workato.com/en/connectors/servicenow#…
1
🙌1
Shiva
·
·
Hi dkuroda Good morning I hope you are doing well This happens because switching from polling to a real-time trigger changes how ServiceNow needs to authorize Workato. Real-time triggers work by creating a Business Rule record in the sys_script table — that Business Rule is what fires the webhook to Workato whenever a new incident is created. Your connected user needs explicit access control on that table for this to work, which polling never required. The exact permissions you need, per Workato's current docs: The account used for your ServiceNow connection must have a role with these access control rules: Table Type Operation Name BR record read sys_script / sys_script.* BR record write sys_script / sys_script.* BR record create sys_script BR record delete sys_script
Shonnah H.
·
·
Thank you so much for helping out richy.mulcahy and Shiva love to see the community support! #CommunityStrong
1
Niyaz A.
·
·
Thank you, Shiva, for your continuous support.
🙌1
dkuroda
·
·
Thanks. My google searches came up with a bunch of systematic links and didn't even show the workato page in results on the 1st page. The google AI answer suggested the sys_script ACL, and I got it partially working using just "create". Seeing the other 3 ACLs (4 in total) make sense, but that might be a challenge to get the customer to agree to that. I'll give it a shot, but but if anyone has ideas on how to convey "least privilege" with ACLs that write business rules I could use your suggestions.