Import Set API
Quick answer
Push data into staging tables over REST and let transform maps do the work.
Key takeaways
- Import Set API combines REST push with transform map logic
- It returns the transform result synchronously
- Clean up staging data on a schedule
- Keep transform scripts simple and observable
When to use it
Post to /api/now/import/{staging_table} when the sending system can push but you still want ServiceNow transform maps, coalescing and field mapping to control what lands in the target table.
Synchronous behaviour
The API runs the transform immediately and returns the resulting record sys_id and status. That makes it useful for integrations that need to know the outcome, unlike a scheduled import.
Operational advice
Staging tables grow fast.
- Schedule cleanup of old import sets and rows
- Keep the transform map simple, complex scripts here are hard to debug at volume
- Return errors to the caller rather than swallowing them
- Use a dedicated integration user so volume is attributable
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
Where does an Import Set API payload land first?
- A. The target table
- B. A staging table
- C. The event queue
- D. sys_import_log
Show answer
B. A staging table
Rows land in staging and are then transformed.
What is the main advantage over a scheduled import?
- A. Lower licence cost
- B. Synchronous result for the caller
- C. No transform map needed
- D. It bypasses ACLs
Show answer
B. Synchronous result for the caller
The caller learns the outcome immediately.