Custom workflows · n8n
Public tenders,as triggers in n8n.
procuris delivers events to your flows in n8n, meaning new tenders, changes, moved deadlines and hits of your saved searches. From there they go to the systems your team has already connected in n8n.
What arrives
What arrives in {name}and when.
- Every event
- The six webhook events, filtered per flow by event and saved search.
- The full record
- Each message carries the whole tender, so no second request is needed.
- Signed messages
- Each message is signed according to Standard Webhooks. Your flow checks that it comes from procuris.
- 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, with both. procuris only needs a reachable address of your flow.
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.
Also included
Other systems
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.