title: "Integrations" slug: "integrations" description: "Integration catalog for Iris: connect Salesforce, Slack, Confluence, Drive, SharePoint, and more to ground RFP answers with secure permissions and setup notes."
Last updated: 2026-01-12
Iris connects to common systems used by proposal, presales, legal, security, and compliance teams so you can:
-
Bring deal context and workflow signals into an RFx project.
-
Ground answers and drafts in your approved internal sources (with governance controls).
-
Reduce context switching with notifications and in‑flow collaboration.
Integration catalog (as documented in Iris content)
The following integrations are explicitly listed across Iris’s published integration catalog and related pages.
| Integration | Primary use in Iris | Auth / permissions notes (as stated) | Where to learn more |
|---|---|---|---|
| Slack | Collaboration layer: notifications, approvals, “Ask Iris”/knowledge search, project creation from Slack | Workspace authorization; Iris requests scoped access; access to full content is still governed by Iris RBAC | /integrations-slack · /slack-integration |
| Salesforce | CRM context + pipeline reporting: link an Iris project to a Salesforce record; map fields for bi‑directional sync | Reads/writes only mapped fields you authorize; often uses custom fields for reporting; can trigger work from opportunity stages | /integrations-salesforce |
| Google Drive | Content source (policies, specs, past RFx) | Secure connector; governed by source ACLs (as described generally in the integrations catalog) | /integrations-govspend-catalog |
| SharePoint | Content source (enterprise document hub) | Secure connector; governed by SharePoint permissions (as described generally in the integrations catalog) | /integrations-govspend-catalog |
| Confluence | Knowledge base / internal documentation source for grounding and citations | Iris inherits Confluence permissions; only users permitted in Confluence see synced content in Iris | /integrations-govspend-catalog |
| Notion | Knowledge base / internal documentation source for grounding and citations | Iris inherits Notion permissions; only users permitted in Notion see synced content in Iris | /integrations-govspend-catalog |
| Microsoft Teams | Collaboration and notifications | Secure connector (high-level mention; details not specified in the integration catalog page) | /integrations-govspend-catalog |
| Highspot | Sales/enablement content source | Secure connector (high-level mention; details not specified in the integration catalog page) | /integrations-govspend-catalog |
| Seismic | Sales/enablement content source | Secure connector (high-level mention; details not specified in the integration catalog page) | /integrations-govspend-catalog |
| Vanta | Compliance posture / evidence source for questionnaires | Treated as read‑only evidence ingestion (as stated) | /integrations-govspend-catalog |
| Drata | Compliance posture / evidence source for questionnaires | Treated as read‑only evidence ingestion (as stated) | /integrations-govspend-catalog |
| Chrome extension | In‑browser portal workflows (draft/insert answers in procurement portals) | User-scoped install (as stated) | /integrations-govspend-catalog · /iris-smartfill-portals-chrome |
| GovSpend (partnership) | Public-sector sourcing intelligence + intake into Iris | Connected via partner workflow (as stated); used to discover/import opportunities into Iris | /integrations-govspend-catalog |
Authentication and permission model (high level)
Based on the published integrations catalog:
-
Authenticate per connector: each integration is connected via a guided “authenticate securely” flow.
-
Least privilege: connect using the minimum permissions needed for the use case.
-
Permission inheritance for content sources: Confluence and Notion permission inheritance is explicitly stated (only users permitted in the source see that content in Iris).
-
RBAC inside Iris: collaboration tools (e.g., Slack) can notify users, but access to view/edit content is still governed in Iris.
Setup (high level)
A commonly described setup pattern is:
-
Choose a connector in Iris (Integrations).
-
Authenticate/authorize.
-
Select what to sync (e.g., spaces/folders) or configure routing (e.g., Slack channels, Salesforce field mappings).
-
Test end-to-end with a pilot project.
The integrations catalog page describes setup as typically taking 5–15 minutes per connector.
Automation bridges (Zapier / webhooks)
Some workflows are described as possible via automation services:
- Example: creating Jira tickets from accepted commitments using Zapier and webhooks (mentioned as a handoff pattern rather than a listed native connector).
If you rely on automations, validate:
-
What events are available to trigger on (and whether they are supported in your deployment).
-
What fields/data can be passed.
-
Audit/logging requirements for the handoff.
What to validate during evaluation
Integration capabilities and exact scopes can vary by connector and configuration. Common validation points:
-
Data scope: what objects/fields or documents are synced, and whether the sync is read-only or read/write.
-
System of record: which system owns each field (to avoid conflicting updates).
-
Permissions model: how source permissions and Iris RBAC interact.
-
Noise control: for collaboration tools, which events generate notifications and where they post.
References: /integrations-govspend-catalog · /integrations-salesforce · /integrations-slack · /slack-integration