Connect your stack
Works with the tools you already run.
Connect your everyday work tools to sign in quickly, read your existing bid documents safely, and receive deadline reminders where your team chats. We read from the systems you connect and never write back to them.
Document sources · read only
Read your documents where they live.
Your answer library is already written. It is in your previous bids, sitting in the storage folders your team already uses, and Velstrian Bid reads it there rather than asking you to upload it again.
-
SharePoint
Sites.Read.All
Permits reading bid documents stored in SharePoint. It cannot edit, move, or delete your files.
-
OneDrive for Business
Files.Read.All
Permits reading bid files in your team OneDrive for Business. It cannot edit or delete your files. Personal OneDrive accounts are not supported.
-
Confluence Cloud
Your own permissions
Connects using an API token from your account. It can only open the documentation spaces you already have permission to view, with no extra access.
Every scope above is a read permission. Your files stay exactly where they are, as they are, and your tenant settings stay as you set them. SharePoint and OneDrive are granted by your own Microsoft administrator, so you can see exactly what was consented to and withdraw it without asking us.
Connecting a document source comes with every paid Velstrian Bid plan. For SharePoint and OneDrive, your Microsoft administrator registers an app in your own Microsoft Entra tenant and grants it read access. Confluence needs only an API token from your own account.
Identity and single sign on
Use the directory you already administer.
Single sign on through any SAML 2.0 identity provider, with users provisioned and deprovisioned from your directory rather than from a spreadsheet.
-
Okta
SAML 2.0, sign-in only
Connects to your Okta portal for single sign on, confirming team members when they log in without storing separate passwords.
-
Microsoft Entra ID
SAML 2.0, sign-in only
Connects to Microsoft Entra (formerly Azure AD) for single sign on, letting your team log in with their existing Microsoft work accounts.
-
Google Workspace
SAML 2.0, sign-in only
Connects with Google Workspace so your staff can log in using their standard company Google accounts.
-
Ping Identity
SAML 2.0, sign-in only
Connects to Ping Identity with verified cryptographic signatures to confirm who is signing in.
-
OneLogin
SAML 2.0, sign-in only
Standard single sign on setup for OneLogin accounts with no extra software to install.
-
Any SAML 2.0 provider
SAML 2.0, sign-in only
Works with any standard identity provider or self-hosted login service that supports SAML single sign on.
What comes with it
- SCIM 2.0 provisioning, so joiners and leavers are handled automatically by your company directory
- Domain verification by DNS record before a company domain can be claimed
- Signed assertions required: an unsigned assertion is rejected rather than trusted
- Enforcement, so an organisation can require single sign on and close the password route
There is no app to install at your end and no provider-specific path in our code. You give us an entity ID, a sign-on URL and a signing certificate, which is why the list above is examples rather than a limit. OIDC is not supported yet, and is on the roadmap rather than in the product.
Collaboration · outbound
Alerts where your team works.
Push a deadline or a delivery-evidence reminder straight into the channel your team already checks, and write an evidence export into a folder you choose.
-
Slack
chat:write
Sends deadline reminders and status alerts into your chosen Slack channel. It never reads your channel history or files.
-
Microsoft Teams
ChannelMessage.Send
Sends notifications into your chosen Teams channel. It cannot modify settings in your Microsoft account.
-
Google Drive
drive.file
Saves exported bid packs into a folder you choose, and cannot open or view any other files in your Google Drive.
These three write, which is the whole point of them, so they are named here rather than folded into the read-only list above. Each one goes outward to a channel or a folder you configure, and none of them is a source we read from. A connector is authorised per organisation and can be disconnected from the same screen it was connected on.
Outbound webhooks
Wire Velstrian Bid into the tools you already automate.
A rule can post its event to any URL you own, so a deadline in Velstrian Bid can start a workflow in whatever your team already runs.
What the webhook gives you
- A URL you set, on any host you control, with no app to install at either end
- An optional secret header, so the receiver can prove the request came from us
- The event and the record it fired on, as structured data (JSON), in the request body
- No inbound access: a webhook is something we send outward, never a way in
This is deliberately a plain HTTP POST rather than a badge for a named automation platform. Anything that accepts an incoming webhook can receive it, and nothing on this page claims a packaged integration we have not built.
Automation rules
Trigger, condition, action.
Build a rule in the app: pick an event, set the conditions that matter, and choose what happens. No engineering ticket required.
-
Trigger
When an event happens
A tender deadline is approaching. Velstrian Bid checks for upcoming deadlines once a day and starts the notification rules you set up.
-
Conditions
Filters you choose
Decide how many days in advance you want a reminder: 7, 14, 30, 60, or 90 days before the deadline.
-
Action
What happens next
Send an alert to a web address (webhook), send an email notification, or show an alert inside the app to the assigned person.
One trigger runs today, and it is the deadline sweep: Velstrian Bid checks once a day for tender deadlines inside the window you set and fires the rules that match. We add each further trigger to this page when it runs.
E-sourcing, CRM and agents
Hand off to the systems that own the next step.
Velstrian Bid prepares the work and passes it on. It never lodges a bid for you.
-
E-sourcing portals
Velstrian Bid prepares the submission pack for Jaggaer, Atamis and In-tend and checks it against the portal's requirements. You submit it, in the portal, under your own account.
-
Salesforce and HubSpot
Push your bids into the CRM with the stage mapping you set, and pull CRM changes back into the bid. A change that would overwrite an edit in Velstrian Bid is held for you to review rather than applied.
-
AI assistants, over MCP
Two Model Context Protocol (MCP) connections let an AI assistant such as Claude work with Velstrian Bid. The read only connector looks up your bids and answers. The read and write server can also work on them. Each acts for your organisation through a Velstrian API key you create, and reads only your own organisation's data.
-
The Integrations package
API keys, outbound webhooks, automation rules, the REST API and the MCP server make up the Integrations package. It is included on Portfolio, a paid add-on on Pro, and not offered on Starter.
Connect once, bid from one place.
Every connector reads only what it needs, cites the statute behind each figure, and keeps your data in the EU.