đź“‚ SharePoint is now available on Pickaxe

You can now use SharePoint across Pickaxe in two powerful ways: Actions and the Studio Knowledge Base.

SharePoint is Microsoft’s platform for document management and intranets. Teams rely on it to collaborate, store files, and organize internal content securely. Pickaxe now plugs directly into that workflow.

Two ways to use SharePoint on Pickaxe

1) SharePoint as an Action
Use SharePoint inside conversations to fetch or work with documents dynamically. Perfect for internal assistants and workflows.

Credentials (this part is really cool):

  • Use Owner’s credentials
    The action runs using the builder’s SharePoint access.

  • Use User’s credentials
    Each end user connects their own Microsoft account, so the Pickaxe only sees what they are allowed to see.

No shared logins. No permission headaches. It respects SharePoint access exactly as intended.

sharepoint gif

2) SharePoint in the Studio Knowledge Base

You can also connect OneDrive & SharePoint directly to your Knowledge Base. This lets your Pickaxes answer questions using documents stored in SharePoint, just like other KB sources.

This is great for:

  • Internal documentation

  • Policies, SOPs, and handbooks

  • Team or company knowledge assistants

Once connected, your Pickaxe can reliably reference that content without needing it uploaded manually.

If you’re already living in SharePoint, this makes Pickaxe feel like a natural extension of your workspace.

Have fun building, try it out, and let us know what you create.
Happy building and happy holidays :christmas_tree::sparkles:

4 Likes

Regarding these accesses, is there way to limit how much resources Pickaxe uses on them? I noticed that trying to look for data (for example latest file) in Google Docs for example or Google Analytics takes a lot of tokens. (Even with a small amount of files in Google Drive) and even when only asking for “file name”.

Totally fair concern. This catches a lot of people once they start connecting live data sources.

What’s happening under the hood
Every time a query runs, Pickaxe has to check the connected source. If a Knowledge Base or Action is set to be checked every time, the system scans the entire connected dataset to see what might be relevant. That work happens even if the final answer is just a file name or even if nothing useful is found.

Imagine this:
It’s like asking someone to search an entire filing cabinet just to answer “what’s today’s date.” The answer is obvious, but because you asked them to check, they still open drawers, skim files, and do the work anyway. That effort takes time and money, even though the final answer is simple.

Why tokens add up quickly
If you connect multiple KB sources, for example Google Drive plus SharePoint, each query triggers checks across both systems. More sources means more scanning. More scanning means more token activity. That’s why even very basic questions can look surprisingly expensive.

Easiest way to see real costs
The simplest way to understand what’s actually happening is to look at the Message Insights in your Studio Dashboard. Go to Users → Activity, then click the insights icon next to a message. You’ll see the exact token count, dollar cost, and whether the Knowledge Base was used.

(Screenshot: Even for something as simple as “what is 1+1?”, you’ll notice token usage if the Knowledge Base is enabled and set to check every time.)

A few practical tips

  • Only enable KBs or Actions on Pickaxes that truly need them

  • Avoid “always check” setups for tools that mostly answer lightweight questions

  • Split tools: one Pickaxe with heavy KB access, another without

  • Keep connected folders and sources as narrow as possible

Nothing is broken here. These integrations are powerful, but they’re doing real work every time they run. Once you see the breakdown in Insights, it becomes much easier to design Pickaxes that balance capability, speed, and cost.

Happy to help you tune a specific setup if you want to go deeper.

Thank you for the answer. Was thinking of creating one “super” access to all Google tools since that is now possible, but it really ads up on the cost very very very quickly as you said.

Hopefully there will soon be more optimized connections to different tools so it doesn’t take so much tokens to get simple data from Google Analytics / Drive / Docs etc. for example.

Unfortunately this is not something Pickaxe can really do anything for now since those things are all on the shoulder of Google and other devs to create these path ways for their tools and more importantly the data they “hoard” to be accessed by AI tools more efficiently.

I have connected it and it is not accessing my company drive.

Hi @rezinhowes, Welcome to the community :waving_hand:

If SharePoint isn’t being accessed, the fastest way for us to help is to take a quick look.

Please email info@pickaxe.co with:

  • The link to your Pickaxe

  • A screenshot of the Knowledge Base or Actions page where SharePoint is connected

  • A screenshot or exact error message, if you’re seeing one

Once we have that, we can check the setup and permissions on our side and help get it sorted quickly.