Hello, I confess I’m new to API and while I do understand the premise I’m not up to speed on the specific execution and I’m a little unclear on the structure.
I’m trying to do the following in basic English: When an item gets added to a board in Monday.com I want to create a sharepoint folder and then e-mail a link to that folder to an employee. Since it’s an employee they would just be able to click on the link and go to the Sharepoint folder in their browser.
I have the Monday and Sharepoint folder creation part sorted out. After some digging I saw that Zapier has an “API Request (Beta)” action option so I started poking around that but I’m unclear on exactly what data should be populated into the fields.
Zapier provided a link to this Microsoft page to help get clarification. From there I also found this Microsoft page. I am still unclear on exactly what to put in the fields in Zapier.
Here’s a screenshot of the fields below.
I assume it’s a “GET” request based on context and what I’ve read so far.
From this page I’m thinking the URL should either be https://{site_url}/_api/site or https://{site_url}/_api/web and since I’m trying to get the URL of a specific folder I’m thinking https://{site_url}/_api/web but I could be mistaken. Do I also need to include more in that URL such as some examples I saw that used “GetFolderByServerRelativeUrl”?
Apologies for fumbling into this without knowing much but I thought this would be simpler and I know enough to start digging through stuff but so far I’ve been unable to piece together what might work for this specific application.
If anyone has any suggestions, resources, guidance, etc. on how to accomplish this I would greatly appreciate it. I’m going to continue trying to further educate myself on this but just wanted to post here as well.
Page 1 / 1
It would be strange if the folder was created, but the zap didn’t return the link to the folder or the folder id.
Can you post a screenshot of the output when you test the folder creation step?
I would assume the folder id is returned at a minimum, and since you know which directory you just created it in, can’t you recreate the link using the id?
Here’s a scrubbed copy and paste from the output data of the sharepoint folder creation step. On closer inspection it looks like “Odata ID” might be something useful for the API if I go that route.
But to your point that’s what I thought as well but I didn’t see any information here that was a straight-up URL to the folder that was created. I do see that it might be possible to piece together the URL with some of this info but the URL would have %20 for space characters and I’m not sure how to work around that. I also may very well be over-thinking it.
Odata ID https://[domain].sharepoint.com/sites/[site]/_api/Web/GetFolderByServerRelativePath(decodedurl='/sites/[site]/Shared Documents/[Folder]/IT/zapier test/test 123')
Odata Id Get Folder By Server Relative Path decodedurl='/sites/[site]/Shared Documents/[Folder]/IT/zapier test/test 123'
Odata Edit Link Web/GetFolderByServerRelativePath(decodedurl='/sites/[site]/Shared%20Documents/[Folder]/IT/zapier%20test/test%20123')
Odata Edit Link Get Folder By Server Relative Path decodedurl='/sites/[site]/Shared%20Documents/[Folder]/IT/zapier%20test/test%20123'
Exists true
Exists Allow Throw For Policy Failures true
Exists With Exception true
Is WOPI Enabled false
Item Count 0
Name test 123
Prog ID
Server Relative Url /sites/[site]/Shared Documents/[Folder]/IT/zapier test/test 123
Time Created 2025-07-24T01:02:54Z
Time Last Modified 2025-07-24T01:02:54Z
Unique Id [unique ID]
Welcome Page
What is the Unique ID? Isn’t that the folder ID just created?
And don’t you know in which folder you told it to create it in?
Screenshots of the configuration tab of folder creation step would be helpful as well.
Unique ID is an alphanumeric string that looks like this: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
I know what folder I am creating these folders in, I’m not sure I follow the reason for the question.
The configuration tab of the folder creation step looks like this - not much info so I didn’t think it was necessary before. “Pulse Name” is the name of the item that comes from the Monday board.
I'm using SharePoint and it simply doesn't work that way. Microsoft controls the URL structure through their ecosystem and the above information is the data available.
Thanks for your attempt to help, I'll continue educating myself to work through this. And of course if anyone more specifically familiar with SharePoint URL structure and API sees this feel free to chime in.
@BrianR if you’re not that comfortable directly writing API requests just yet, another option is to use Zapier’s newer Custom Actions feature: https://zapier.com/l/custom-actions. This gives you an AI chatbot that can help you build a an action that’s not supported by the standard Zapier integration, but that is possible via API. Essentially, you describe what you want to the chatbot and it writes the API request for you. Once the action is built and working, you can re-use it in multiple Zaps and it’s available to everyone in your workspace.
There’s also a tab that you can click into to see the raw API request that the AI has written, so it’s also useful for learning.
Here’s an example of one that I built and recently shared about Notion:
Thank you, I'll definitely check that out.
@BrianR if you’re not that comfortable directly writing API requests just yet, another option is to use Zapier’s newer Custom Actions feature: https://zapier.com/l/custom-actions. This gives you an AI chatbot that can help you build a an action that’s not supported by the standard Zapier integration, but that is possible via API. Essentially, you describe what you want to the chatbot and it writes the API request for you. Once the action is built and working, you can re-use it in multiple Zaps and it’s available to everyone in your workspace.
There’s also a tab that you can click into to see the raw API request that the AI has written, so it’s also useful for learning.
Here’s an example of one that I built and recently shared about Notion:
Just wanted to follow up and say this approach worked very well and got me what I needed. I also realized I was in fact able to piece together a URL and then use HTML to make that a link in the body of an e-mail. I got what I wanted with the custom editor and didn’t have to use API this time either. Will definitely keep it in mind in the future too.
Thank you again!
Glad to hear it, @BrianR! Yeah, Custom Actions is a great feature that a lot of folks don’t know about yet. Even if you are comfortable writing API calls directly, I still often prefer Custom Actions because then I can reuse the same action in a bunch of places and share them with teammates.
