ServiceNow Best Practices · LessonBy Sneha I, ServiceNow Trainer, 8 yrs · Published · ServiceNow · all levels
Integration best practices
Design integrations that survive volume, outages and staff changes.
Quick answer
Design integrations that survive volume, outages and staff changes.
Key takeaways
- Name owners on both sides and document the contract
- Dedicated least privilege integration accounts
- Timeouts, retries and idempotency are not optional
- Alert on error rate, not on every single failure
Contracts and ownership
Every integration needs a named owner on both sides, a documented payload contract and an agreed error path. Most integration incidents are really ownership incidents: something changed and nobody told the other team.
Technical defaults
A short list of defaults prevents most production problems.
- Dedicated integration user with least privilege, never a personal account
- Connection alias and credential records, never hard coded endpoints or secrets
- Timeouts on every outbound call and retry policy for transient errors
- Idempotent operations keyed on a client reference so replays are safe
- Payload limited to fields you use, so upstream changes break less
Observability
Log a correlation id on both sides, alert on error rate rather than single failures, and keep a dashboard that shows volume and latency per integration. When something breaks at 2am, the person paged needs to see which integration and how long it has been failing.
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What makes a replayed message safe?
Frequently asked questions
Should integrations use admin?
No. Grant the specific roles required and test with that account. Admin integrations become a security finding sooner or later.
How do we handle breaking changes from a partner?
Version the contract, monitor error rate, and keep the payload narrow so unrelated changes do not break you.