title: "Salesforce + Slack + Confluence for RFP Responses" slug: "integrations-salesforce-slack-confluence" description: "How Iris connects Salesforce, Slack, and Confluence for RFP workflows: sync deal context, route approvals in Slack, and cite Confluence knowledge securely."

Last updated: 2026-01-12

This page summarizes how Iris can be used with Salesforce, Slack, and Confluence to run a connected workflow for RFPs, RFIs, DDQs, and security questionnaires—linking deal context (Salesforce), in‑flow collaboration (Slack), and a permissioned internal knowledge base (Confluence).

What each integration is used for

Salesforce (deal context + pipeline visibility)

As described in Iris’s Salesforce integration documentation:

• Associate an Iris project (RFP/questionnaire) to a Salesforce record (commonly an opportunity or account).

• Read from Salesforce into Iris: ingest mapped opportunity/account fields needed for RFP work (examples given include deal name/owner/stage/amount/close date and customer-defined fields).

• Write from Iris back to Salesforce: push RFP execution signals back to CRM (examples given include RFP status, key milestones, and outcome/win‑loss signals), typically via mapped (often custom) fields.

• Bi-directional sync: updates to mapped fields can propagate between systems.

• Stage-based triggers: Iris can start or update RFP work when opportunities reach defined stages.

Slack (notifications, approvals, and in‑channel Q\&A)

As described in Iris’s Slack integration documentation:

• Iris → Slack: send messages when workflow events occur (examples include project created/assigned/needs review/submitted), to channels or DMs.

• Slack → Iris: record actions back in Iris via interactive workflows (examples include approve a response, request changes, acknowledge tasks).

• Slack → Iris (knowledge retrieval): “Ask Iris” / Slack commands can query Iris knowledge so users can find approved answers and snippets.

• Setup is described as OAuth authorization + choosing routing (channels/DMs) + enabling optional interactive workflows and knowledge search.

Confluence (permissioned knowledge source)

As described in Iris’s integrations catalog page:

• Confluence is treated as a content source for internal documentation.

• Iris can sync Confluence spaces and use Confluence content as grounded source material (with citations).

• Permission inheritance is explicitly stated: Iris inherits Confluence permissions so only users permitted in Confluence can see the synced content in Iris.

What “syncs” (based on published details)

Because “sync” means different things per system, here is what is explicitly described:

• Salesforce: mapped fields and status signals can be read/written between Iris and Salesforce (bi-directional) based on what you authorize and map.

• Slack: workflow notifications and interactive actions sync between Iris and Slack; Slack messages can include links back to Iris.

• Confluence: Confluence pages/spaces are synced as a governed knowledge source into Iris; access follows Confluence permissions.

Typical end-to-end workflow

1. Intake

2. New RFP arrives; create an Iris project.

3. Link the project to the relevant Salesforce opportunity for deal context.

4. Notify stakeholders in Slack.

5. Draft

6. Iris drafts responses grounded in your approved sources (including Confluence content you’ve connected).

7. Review and approvals

8. Review happens in Iris with role-based permissions and auditability.

9. Slack can be used to route review requests and capture approvals/feedback via interactive actions.

10. Pipeline reporting

11. Iris pushes project status/milestones back to mapped Salesforce fields so the deal team can track progress in CRM.

Setup checklist (high level)

1. Connect Confluence (content source)

2. Authenticate and choose which Confluence spaces to sync.

3. Confirm permission inheritance behavior meets your security requirements.

4. Connect Salesforce (CRM)

5. Authorize access with least-privilege credentials.

6. Decide which record type to link (often opportunities).

7. Configure field mappings (Salesforce → Iris for context; Iris → Salesforce for status/reporting).

8. Configure any stage-based triggers you want to use.

9. Connect Slack (collaboration)

10. Install/authorize via OAuth.

11. Choose where notifications should land (channels vs DMs).

12. Enable interactive approvals and knowledge search features as needed.

13. Pilot and validate

14. Test end-to-end on a small set of opportunities and one active RFP.

15. Confirm that Slack notifications don’t expose content beyond what users can access in Iris.

Known limitations / details not specified in published docs

• Salesforce: the exact objects/fields supported depend on your configured mappings; only authorized fields are read/written.

• Slack: message content and interactive actions depend on how your workspace is configured; access to full response content is still governed in Iris.

• Confluence: published content states space sync + permission inheritance, but does not enumerate specific Confluence object types, page filters, or refresh intervals—omit assumptions and validate during setup.

References: /integrations-salesforce · /integrations-slack · /integrations-govspend-catalog · /slack-integration · /salesforce-and-slack-integrations