What are the required details for integrartoin?

[Ankur Bawiskar]

@gupta-am 

here are few links for requirement gathering for integrations

Technical Requirement Gathering for an Integration 

Requirements Gathering for ServiceNow Integrations 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Dr Atul G- LNG]

Hi @gupta-am 

Here is my video, where I’ve shared all the required details. You can also refer to Now Create for the basic information. The video below should be helpful.

https://youtu.be/DjoPIyqvum0

[Aniket Chavan]

Hello @gupta-am ,

To give you a better answer, it would really help if you could share a bit more detail about what you’re looking to do. Are you trying to integrate ServiceNow with another platform like Salesforce, Azure DevOps, SAP, or maybe even another ServiceNow instance? Or are you just exploring the general process and curious about what’s typically required?

Integrations can vary a lot based on the use case — and gathering the right info upfront makes a huge difference. I've worked on a few integrations myself, and I’ve seen that the hardest part is usually not the actual development.

ServiceNow gives you solid tools for REST, SOAP, Flow Spokes, etc. The real challenge is asking the right questions before you start building.

Here are a few things we usually try to clarify before starting:

🔹 What’s the purpose of the integration? Is it for data sync, triggering workflows, reporting, or just visibility?
🔹 What’s the data flow like? Will data flow one way (outbound/inbound) or both ways (bi-directional/eBonding)?
🔹 What will trigger the integration? Something like a record update, assignment, status change, or will it run on a schedule?
🔹 What kind of data and how much? Knowing whether you’re syncing a few records a day or a million a week will shape how it’s built.
🔹 Do the systems support modern integration methods? Some older platforms might not have APIs or might need workarounds.
🔹 Security concerns? Think about firewalls, VPNs, or if you’ll need a MID server. Also: will sensitive data need to be encrypted at rest/in transit?
🔹 How will errors be handled? Logging, retries, notifications, etc.

And honestly — sometimes the key people (process owners, system admins, etc.) don’t get looped in early enough, which leads to surprises later. So it’s a good idea to involve the right stakeholders during planning, especially when multiple tools or teams are involved.

If you’re still in the early stages and just mapping things out — that’s totally fine! You can also refer to the great references shared by @Ankur Bawiskar  and @Dr Atul G- LNG  in this thread — they cover some thoughtful points around integration requirement gathering that might help shape your approach.

But if you could clarify what tools/systems are involved or what your end goal is, I or someone else from the community would be happy to guide you.

🔹 Please mark ✅ Correct if this solves your query, and 👍 Helpful if you found the response valuable.

Best regards,
Aniket Chavan
🏆 ServiceNow MVP 2025 | 🌟 ServiceNow Rising Star 2024

[Dr Atul G- LNG]

Experience writing 🙂 well @Aniket Chavan