Integration Platform

API-First Design

Every feature in Fluvial’s user interface is accessible through REST APIs. This includes questionnaire management, response collection, workflow control, analytics, and user administration.

OpenAPI Documentation

All APIs follow OpenAPI 3.1 specifications, providing interactive documentation and enabling automatic client library generation for different programming languages.

// Example: Create questionnaire and trigger workflow
const questionnaire = await fluvial.questionnaires.create({
  title: "Vendor Security Assessment",
  sections: vendorSections,
  workflow: "security-review"
});

await fluvial.workflows.transition(questionnaire.id, 'security-review', {
  assignTo: 'security-team@company.com'
});

Webhook System

Fluvial sends HTTP notifications when events occur, such as response submissions, workflow transitions, or user actions. Webhooks can be configured to filter events by type, project, or content conditions.

Delivery Reliability

sequenceDiagram
    participant Z as Fluvial
    participant W as Webhook Endpoint
    participant R as Retry Queue
    
    Z->>W: Event Notification
    alt Success Response
        W->>Z: 200 OK
    else Failure Response
        W->>Z: 4xx/5xx Error
        Z->>R: Queue for Retry
        R->>W: Retry with Backoff
    end

Failed webhook deliveries are automatically retried with exponential backoff. Permanently failed events are captured for review, and all deliveries include cryptographic signatures for verification.

Workflow Automation

Webhooks can trigger external automation when questionnaires transition between workflow statuses. The webhook payload includes response data, scores, and context that receiving systems can use to execute business logic.

Example Webhook Payload:

{
  "event": "workflow.transition",
  "questionnaire_id": "q_12345",
  "from_status": "security-review",
  "to_status": "approved",
  "scores": {
    "overall": 85,
    "security": 90,
    "compliance": 80
  },
  "responses": { /* response data */ },
  "user": { /* user context */ },
  "timestamp": "2025-10-17T10:30:00Z"
}

Conditional Execution with CEL

Webhook delivery can be controlled using Common Expression Language (CEL) guard expressions:

// Only trigger for high-risk assessments
scores.overall < 50

// Trigger for specific workflow transitions
transition.to == 'approved' && scores.security > 75

// Complex conditional logic
risk_level == 'high' && department == 'finance' && approval_count < 2

Data Transformation

CEL expressions can also transform webhook payloads before delivery, allowing you to extract specific fields, calculate derived values, or format data for external systems:

{
  'vendor_id': questionnaire.vendor_id,
  'risk_score': scores.overall,
  'status': transition.to,
  'requires_review': scores.overall < 60,
  '
}

This approach keeps business logic in your systems rather than locked in platform configuration. Automation can be implemented in any language that handles HTTP requests, tested independently, and scaled separately from the questionnaire platform.

Enterprise System Integration

CRM and ERP Systems

Fluvial can integrate with customer relationship management and enterprise resource planning systems to automate vendor creation, update risk profiles, and trigger due diligence workflows.

Webhook-Based Salesforce Example:

Configure a webhook with a CEL transformation expression to map Fluvial event data to Salesforce’s expected format:

// CEL transform expression for Salesforce opportunity update
{
  'opportunity_id': questionnaire.opportunity_id,
  'fields': {
    'Due_Diligence_Score__c': scores.overall,
    'Due_Diligence_Status__c': transition.to == 'approved' ? 'Complete' : 'In Progress',
    'Risk_Rating__c': scores.overall >= 80 ? 'Low' : 
                      scores.overall >= 60 ? 'Medium' : 'High',
    'Next_Review_Date__c': scores.overall >= 70 ? 
                           timestamp.addDuration(duration('365d')).format('2006-01-02') :
                           timestamp.addDuration(duration('90d')).format('2006-01-02'),
    'Security_Score__c': scores.security,
    'Compliance_Score__c': scores.compliance,
    'Requires_Manual_Review__c': scores.overall < 60
  }
}

This transformation runs within Fluvial before the webhook is delivered, eliminating the need for intermediate processing services. The webhook endpoint receives data already formatted for Salesforce’s API.

Document Management

Document automation systems like SharePoint, DocuSign, and Box can be integrated for automatic filing, signature workflows, and secure file sharing during the questionnaire process.

Integration Patterns

Legal Due Diligence Automation

flowchart TD
    A[Deal Opportunity Created] --> B[Fluvial API Triggered]
    B --> C[Questionnaire Auto-Generated]
    C --> D[Target Company Notified]
    D --> E[Responses Collected]
    E --> F[Webhook: Risk Analysis]
    F --> G{Risk Level?}
    G -->|Low| H[Auto-Approve]
    G -->|Medium| I[Senior Review Required]
    G -->|High| J[Committee Escalation]
    H --> K[Update CRM]
    I --> L[Assign to Senior Analyst]
    J --> M[Create Executive Report]
    K --> N[Trigger Contract Process]
    L --> O[Review Complete]
    M --> P[Schedule Committee Meeting]

Financial Services Compliance

sequenceDiagram
    participant R as Regulatory System
    participant Z as Fluvial
    participant C as Compliance Team
    participant A as Audit System
    
    R->>Z: Compliance Requirement Change
    Z->>Z: Auto-Update Questionnaire Templates
    Z->>C: Notify via Webhook
    C->>Z: Review and Approve Changes
    Z->>A: Log Compliance Event
    Z->>R: Confirm Implementation

Developer Resources

SDKs are available for Python, JavaScript, Java, C#, and Go. The platform provides sandbox environments for testing integrations, detailed error codes for troubleshooting, and performance monitoring for API response times and success rates.

Getting Started

Organizations typically begin by exploring the OpenAPI documentation, configuring webhooks for critical business processes, and implementing a pilot integration to validate the approach. After successful validation, additional systems can be connected to build comprehensive process automation.

---