ServiceNow → SharePoint Integration to Automatically Save Scheduled Reports (PDF/Excel)

aparnaravi
Tera Contributor

Hi Community,

We have a requirement to integrate ServiceNow with SharePoint so that reports can be automatically generated on a weekly basis and saved in SharePoint as PDF/Excel files.

Requirement details:

  • Reports are built in ServiceNow (Incidents, Requests, SLA, etc.)

  • Reports need to be scheduled weekly

  • Output format: PDF / Excel

  • Files must be automatically stored in a SharePoint document library

  • No manual download or upload should be required

We understand that ServiceNow does not provide an out-of-the-box option to directly save reports or dashboards to SharePoint.

We would like guidance on:

  1. The recommended approach for this integration

  2. Whether using Microsoft Graph API + OAuth is the best practice

  3. Any existing plugins, integrations, or examples for uploading report files to SharePoint

  4. If anyone has implemented a similar solution, what challenges or limitations should we be aware of

Any suggestions, reference implementations, or best practices would be greatly appreciated.

Thanks in advance

4 REPLIES 4

Mark Manders
Mega Patron

Since scheduling them is always an export to email, you could also check on the possibilities you have from there. If you have an email address you are sending them to and you can manage storing them in sharepoint with logic from the email client, you don't need to customize ServiceNow for it.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Hi @Mark Manders 
Rather than scheduling the reports to be emailed, the customer wants to save the reports in PDF or Excel format in SharePoint, so an integration is required.

It could be easier to create that integration from the email client to sharepoint, since that's probably all Microsoft. I haven't come across a 'saving reports on sharepoint' integration from ServiceNow yet.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

BillMartin
Giga Sage

Hi @aparnaravi ,

 

Thanks for sharing your use case. As a general best practice, we try to limit heavy customization in ServiceNow, but when a requirement is critical and not available out of the box, a well-designed integration is absolutely appropriate.

 

For integrating ServiceNow with SharePoint, I’d recommend:

 

  1. Build for reliability and security with proper error handling, logging, and OAuth (Microsoft Graph API is commonly used).

  2. Use the Event Queue (sysevent) for asynchronous processing instead of running heavy logic synchronously. This improves performance, traceability, and recovery, and is the same mechanism used for notifications and background automation.

  3. Apply resilience patterns like circuit breaker, retries, and timeouts to protect the platform from external instability.

  4. Expose the integration via Flow Designer custom actions so it’s reusable and easy to govern across workflows.

I’ve created a step-by-step integration tutorial series that covers these best practices here:
👉 Rest-API Foundations 

 

Hope this helps. Let me know if you have any questions.

 

If you find the reponse lucrative please mark as helpful and accept as solution

In this playlist, you will learn the basics and gain a firm understanding of integrating both inbound and outbound applications. Explore the security archite...