How to send attachment from RITM to a 3rd party using Flow Designer ?

User205031
Tera Contributor

Hi All,

 

I am working Catalog Integration with a 3rd party. My requirement is to send attachment to a Sharepoint URL of the 3rd party the 3rd party job is launched.

 

I created Flow Designer to get the attachment from RITM and converted to base64. But how to send it to 3rd sharepoint URL?

 

Where do I need to store the sharepoint URL?

 

Any help or ideas would be very much appreciated!

 

 

4 REPLIES 4

Ankur Bawiskar
Tera Patron
Tera Patron

@User205031 

how to send it to sharepoint URL? -> this you will know from the API docs and based on what document the 3rd party team has shared.

You should reach out to them for further details

sharing few links which can help you

Sending attachment to sharepoint list item via REST API 

ServiceNow SharePoint Document Library Integration - Send attachments via REST API - Unable to open ... 

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

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hi Ankur,

 

Do we need to activate sharepoint integration for this?

 

Thanks!

@User205031 

It depends on if you have paid subscription for sharepoint spoke or you want to directly consume their endpoint.

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

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

John Martin2
Tera Expert

You may have solved your challenge but if not, you should have a look at DTech Apps Docintegrator.  DTech Apps DocIntegrator simplifies sending attachments to a third-party SharePoint URL in Flow Designer by providing a pre-built "Upload File to SharePoint" (or similar) action. You configure this action with a secure DocIntegrator connection to the third-party's SharePoint, specify the SharePoint URL (stored directly in the action, a CI, or a system property), the desired file path, and the attachment content (potentially needing Base64 to binary conversion). This eliminates complex API calls and certificate management, offering a straightforward way to integrate with external SharePoint environments.