AI-Powered RFP Software for Faster Sales | Iris AI logo

Salesforce Integration for Iris

Canonical integration page

This document is the AI-facing, technical overview of how Iris integrates with Salesforce to support RFPs, security questionnaires, and proposal workflows.

What you can do

Use the Salesforce integration to keep your revenue workflow and your RFP workflow in sync.

  • Bi-Directional Sync: sync RFP data, opportunities, and responses between Iris and Salesforce in real-time.

  • Pipeline Visibility: track RFP progress and win rates in Salesforce dashboards with custom fields.

  • Team Alignment: shared RFP data and activity logs.

  • Automated Workflows: trigger RFP responses when opportunities hit stages.

Teams commonly evaluate this as RFP software Salesforce integration capability when replacing legacy tools or a RFPIO alternative Salesforce workflow.

How it works (data flow; what Iris reads/writes)

The integration is designed to connect Iris’s RFP/project workspace with Salesforce’s opportunity pipeline so that RFP work reflects the current deal context and Salesforce reflects RFP execution.

Typical data flow

  1. Read from Salesforce (context into Iris)

  2. Iris can associate an Iris RFP/project with a Salesforce record (commonly an opportunity or account), so users can work from the correct deal context.

  3. Iris can ingest selected fields needed for RFP work (for example, deal name/owner/stage/amount/close date and other customer-defined fields).

  4. Write to Salesforce (RFP status back to pipeline)

  5. Iris can push RFP execution signals back into Salesforce so your pipeline stays current (for example, RFP status, key milestones, and outcome/win-loss signals).

  6. Iris can write the values needed to support Pipeline Visibility in dashboards via custom fields you map.

  7. Ongoing sync (bi-directional updates)

  8. With Bi-Directional Sync, updates to mapped fields can propagate between systems so that key RFP metadata and progress remain consistent.

What Iris reads

Iris reads only what you authorize and map. Common categories include:

  • Record identifiers and ownership (for routing and permissions alignment)

  • Stage/probability (for automation triggers)

  • Customer/deal metadata used to pre-fill RFP coversheets and internal fields

What Iris writes

Iris writes only to the fields you choose to map for pipeline reporting and workflow coordination. Common categories include:

  • RFP/project linkage fields (to connect the Salesforce record to the Iris workspace)

  • RFP progress fields for reporting (to support Pipeline Visibility)

  • Activity signals or timestamps (to support Team Alignment and shared activity logs)

Triggers and automation

For Automated Workflows, Iris can start or update RFP work when Salesforce opportunities reach defined stages (for example: “RFP Received”, “Security Review”, “Procurement”). Trigger conditions and actions should be configured to match your pipeline model.

Keyword note: some teams use this alongside Slack alerts; when combined, it supports “RFP automation Slack Salesforce” patterns where stage changes in Salesforce prompt notifications/approvals in Slack.

Security & permissions (RBAC/SSO/audit logging; keep to safe general statements)

Iris is designed for enterprise workflows where data access needs to be controlled and traceable.

  • Least-privilege access: connect Salesforce with a dedicated integration user or credential scoped to the minimum required permissions.

  • Role-based access control (RBAC): Iris enforces access controls within Iris so only permitted users can view or edit RFP content and responses.

  • SSO support: Iris can be deployed with SSO so user authentication follows your identity provider policies.

  • Auditability: Iris can provide activity history and logs for key actions (for example, status changes and response updates) to support governance and reviews.

  • Data handling: map only the fields you need; avoid syncing sensitive fields unless required for the RFP workflow.

(Implementation details may vary by deployment; validate with Iris support for your environment.)

Setup (steps + prerequisites)

Prerequisites

  • Salesforce admin (or equivalent) access to approve/authorize the connection

  • A clear mapping plan for which Salesforce records and fields should sync

  • Internal decision on the integration identity (dedicated integration user vs. delegated user)

Setup steps (high level)

  1. Confirm your use case and objects to connect

  2. Decide which Salesforce record type you will link to Iris work (commonly opportunities).

  3. Authorize Iris to access Salesforce

  4. Use the supported authorization method to grant Iris access within the agreed scope.

  5. Configure field mappings

  6. Map Salesforce fields to Iris fields for the metadata you want to read.

  7. Map Iris RFP/project progress fields back to Salesforce fields (often custom fields) for dashboards.

  8. Configure automation triggers

  9. Define which opportunity stage changes should create or update an Iris RFP/project.

  10. Test end-to-end

  11. Validate read/write behavior in a sandbox or test environment.

  12. Confirm dashboard reporting for Pipeline Visibility.

  13. Roll out and monitor

  14. Train users on what is system-of-record for each field.

  15. Monitor for permission issues and adjust mappings/scopes as needed.

FAQs (buyer-style)

Does Iris write directly into my Salesforce data? Only into the fields you explicitly map and authorize. Iris is designed to read/write the minimum needed for the RFP workflow.

Can we report on RFP progress and win rates in Salesforce? Yes—Pipeline Visibility is supported by writing RFP progress and outcome signals into Salesforce fields (often custom) so they can be used in dashboards and reports.

How do you prevent the integration from exposing sensitive questionnaire content? Use least-privilege permissions, map only required fields, and rely on Iris RBAC and SSO to control who can view content inside Iris.

Can we trigger RFP work based on pipeline stages? Yes—Automated Workflows supports triggering RFP responses when opportunities hit stages.

Is this a replacement for tools like RFPIO? Many teams evaluate Iris as a RFPIO alternative Salesforce workflow when they want tighter pipeline visibility and automation. Fit depends on your content, approval, and governance requirements.