Data & Integrations
Data and integrations that work with what you have.
Your content, your colleagues and your systems already live somewhere. SEQUESTO meets them there, so a bid starts from what your company knows instead of a blank page and a hunt through folders. Use what's ready, and connect the rest your way.
Three ways to connect
Use one, two or all three. They work side by side. Many teams start with the off-the-shelf integrations, add connectors as James becomes part of their day, and use the API for their own processes.
- 1
Route 1
Off-the-shelf integrations
Switch on in settings, no code. Fill your Knowledge Hub from SharePoint or Google Drive, get updates in Teams or Slack, and sign in with your company account.
- Set up by
- Your SEQUESTO admin
- Best for
- Content, notifications and sign-in, handled once
- 2
Route 2
Connectors for James
Let James, your AI colleague, look things up in the tools your team already uses, while you stay in the conversation.
- Set up by
- Admin turns on, each person signs in
- Best for
- Answers that depend on live information elsewhere
- 3
Route 3
The SEQUESTO API
Connect SEQUESTO to any system you run, in the way your process needs. Your team or your partner builds it once.
- Set up by
- Your IT team or integration partner
- Best for
- Automating the steps around every bid
Route 1
Off-the-shelf integrations
Switch these on in settings. They do three jobs: fill your Knowledge Hub, keep your team informed, and let people sign in.
Fill your Knowledge Hub
Microsoft SharePoint or Google Drive
Choose the site or folders that hold your reference material. SEQUESTO copies the files into your Knowledge Hub and keeps them up to date, including edits, renames and removals at the source.
Never writes back to your storage.
Keep your team informed
Microsoft Teams or Slack
Add SEQUESTO to your workspace, choose a channel and choose what it announces, such as who joined a project or who was assigned to what.
Only posts, never reads your chats. Pause any time.
Sign in with your company account
Microsoft Entra ID, Google Workspace, Okta
Your people sign in with the account they use every day. Invited colleagues are active on their first sign-in, and access ends when IT removes the account.
Route 2
Connectors for James
Some answers live in Confluence, Jira, Salesforce or Teams. James connects through their official connectors (MCP) and fetches them while he helps you, so you stay on the bid instead of switching tabs.
Confluence
Processes, policies, runbooks and product documentation.
Jira
Issues and projects, for today's answer on a feature or a delivery date.
Salesforce
The account, opportunity and contact details behind a bid.
Microsoft Teams
What your team agreed in channels and chats.
Notion
Your pages and wikis.
And many more
Dozens of connectors are on the way. Tell us which ones matter most to you.
“The questionnaire asks how we handle incident response. Check our Confluence runbook and draft an answer in our usual tone.”
James reads the runbook through the Confluence connector, drafts the answer, and tells you which page it came from.
Your admin turns a connector on for the company, then each person connects their own account once.
Route 3
The SEQUESTO API
With the API, your own systems can open projects, hand over files, keep your library current and pull figures back out. Build it once, and the busywork around each bid disappears.
A project opens with the files attached
Your CRM or tender portal creates the project, fills in its details and attaches the tender documents.
Your Knowledge Hub stays current
Send the latest policy, certificate or product sheet. Sending it again to the same place replaces the old version.
Figures flow into your reports
Pull the numbers behind your SEQUESTO dashboards into the reporting tool your company already uses.
Your systems hear about it
SEQUESTO tells your systems the moment a project is ready, so your next step can start by itself.
An admin creates an API key in SEQUESTO settings. The key works only for your company, can be revoked any time, and the full reference documentation is public, so your developers or partner can start straight away.
Connected, and still in your control
Connecting more systems should never mean sharing more than you meant to. Every route follows the same rules.
Your company only
Everything you connect stays inside your company's space. Nothing is shared with other customers.
Your permissions carry over
James uses each person's own account in connected tools, so he never sees more than that person could.
Admins decide
Integrations, connectors and API keys are switched on by your admins, and can be switched off just as easily.
Credentials protected
Connection secrets are stored encrypted, and API keys are shown once and can be revoked at any time.
Questions teams ask
No. The SharePoint integration only reads. Files are copied into SEQUESTO and kept current, and nothing is written back.
No. Each person connects their own account, and James works through it. If you can't open a page in Notion or Confluence, neither can James.
Not for the first two routes. Off-the-shelf integrations and James connectors are switched on in settings. Only the API needs someone to build the connection.
Use the API to bring its content into your Knowledge Hub or to create projects from it. We're also adding more connectors for James. And you can always contact us to request a connection to any other tool: we review every request and will look into what's possible.
Your SEQUESTO admins. They choose what is connected for the whole company, and can disconnect it at any time.