Skip to main content

Custom workflows · Microsoft SharePoint

Public tenders,in your table on SharePoint.

procuris writes new hits as rows into an Excel table on SharePoint. Your team reviews them in one place, adds columns of its own and works on from there.

What arrives

What arrives in {name}and when.

One row per hit
With title, contracting authority, deadline, Fit and a link to the tender in procuris.
Current deadlines
If a deadline moves, procuris updates the row.
Your columns stay
Columns your team adds, such as owner or decision, procuris leaves unchanged.
When it arrives
Hits arrive once in the morning with the run of your saved searches. New and changed tenders, moved deadlines and ended procedures follow up to an hour after procuris has taken over the change.

On request

A quotefor your scope.

You get the API, webhooks and custom workflows through an individual quote. This is the way there.

  1. 01Send a requestThrough the contact form. Tell us what you want to connect, for example new hits into the CRM or a message in Teams.
  2. 02Talk about the scopeWe clarify which services you need, which systems you connect and how often your system fetches.
  3. 03Individual quoteTailored to that scope. If procuris should build the integration, the quote says so.
  4. 04SetupAfter the contract is signed, we set up access for your organization. From then on the person with the Owner role manages tokens and target addresses in procuris.

Frequently asked questions

An Excel table in a document library of your choice on SharePoint. Location and columns we agree with you.
No. procuris sets up the workflow for your organization. You tell us what should go where, and we agree it with you.
Through a request. We agree the scope with you and send you an individual quote. Once the contract is signed, we set up the workflow.

On request

Which system does your team use?We connect procuris to it.

Tell us the system and the flow you have in mind. We agree the scope with you and send you an individual quote.