Inbound REST for event creation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 11:09 AM
Attempting to POST events from a third party system to our instance of SNOW using the Global - Inbound Event URL:
https://snowinstance.service-now.com/api/global/em/inbound_event
We have confirmed the post is authenticating, but we are getting the following response:
"error": { "message": "No Transform script found for given header or source ", "detail": "" }, "status": "failure"
Have attempted to create a listener transform script with a header name of "Application" and value with the name of our application making the call, which was then added to the api call, but this didn't help.
I'm sure I'm missing something simple, very new to this area of SNOW and wanted to use this method as opposed to direct table integration if possible.
Any help is much appreciated!
- Labels:
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2018 01:33 AM
Hi,
which release version do you run? pre-Kinston?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2018 07:50 AM
Thanks Sebastian,
Sorry I forgot to add that important detail.
We are currently developing this on Kingston, and our Prod instance will be updated to Kingston prior to promoting this piece.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2018 11:38 AM
Hello,
did you get the solution?
I am trying to push alerts from Azure to ServiceNow. i am also receiving similar error
logs:
exception=new sn_ws_err.ServiceError().setStatus(400);
exception.setMessage('No Transform script found for given header or source ');
throw exception;
})(request, response);
: no thrown error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2018 12:04 PM
Unfortunately we were not able to resolve this using the Global Inbound Event URL. We reverted to using Table Integration API for the time being until we find some additional documentation on the new method available.