Custom workflows · Confluence
Public tenders,as a page in Confluence.
procuris creates a page in your Confluence space for every matching tender. There your team prepares the decision on a bid, with all key facts in one place.
What arrives
What arrives in {name}and when.
- One page per tender
- With title, contracting authority, deadline, contract value, lots, Fit and a link to procuris.
- A space of your choice
- Pages are created in the space and under the parent page you choose.
- Changed key facts
- If the deadline or description changes, procuris updates the key facts on the page.
- 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.
- 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.
- 02Talk about the scopeWe clarify which services you need, which systems you connect and how often your system fetches.
- 03Individual quoteTailored to that scope. If procuris should build the integration, the quote says so.
- 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
Yes. procuris only maintains the section with the key facts. What your team writes below it stays.
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.