Integration with Amazon Redshift

Learn how to integrate Outdoo's call and deal intelligence with Amazon Redshift to unify conversation data with your existing business analytics and BI workflows.

Introduction

Outdoo's platform analyzes your sales call data (recorded customer meetings) in real-time and deal data (pipeline and CRM opportunities) on scheduled intervals. Integrating this analyzed data into Amazon Redshift allows RevOps and data teams to unify conversation intelligence with other business data.

This allows deeper analysis of deal trends, rep performance, customer behavior, and pipeline risks within your existing BI tools and workflows. Connecting Outdoo to your warehouse lets you correlate call insights and AI-derived deal metrics with CRM, product usage, and revenue data for more informed decision-making.

Integration Overview and Supported Methods

Outdoo provides direct integration options to sync data to your warehouse without requiring third-party ETL tools. The following methods are supported:

REST API Pull: Outdoo offers RESTful APIs to retrieve call and deal data for custom integrations. Advanced customers can use this to script data pulls. This requires more custom development but provides flexibility.

Cloud Storage Stage (S3): Outdoo can export data files in JSON format to an S3 bucket you own. Redshift can then bulk-load from this location. This method is useful if direct database connections are not possible but may introduce slight delays (for example, daily batch file drops).

Security and Authentication Setup

Before starting, ensure you have prepared secure access for Outdoo:

Create Dedicated Credentials: Provision a dedicated user or role in Redshift for Outdoo (for example, a database user or IAM role). Grant only the minimum privileges needed to create and write to Outdoo-specific schemas.

Network Access: If your warehouse is behind a firewall or VPC, whitelist Outdoo's egress IP addresses. Redshift users should allow inbound access from Outdoo's known static IP in their cluster's security group settings.

API Keys and Tokens: Generate secure tokens for REST API connections. Outdoo will securely store any tokens or secrets you provide.

Certificate and Encryption: All integrations use encrypted channels (HTTPS for APIs, TLS for JDBC).

Auditing and Revocation: Treat Outdoo integration credentials as you would any service account. Monitor their activity and rotate keys/tokens periodically. Revoke credentials if the integration is disabled.

Amazon Redshift Integration

Outdoo's Redshift integration uses a secure, role-based approach to push data into your Redshift cluster. This typically involves IAM roles and S3 for staging data, then loading into Redshift.

Setup Steps

Create a Redshift User or IAM Role for Outdoo: Use Redshift's IAM integration for security. Create a new database user (for example, outdoo_writer):

   CREATE USER outdoo_writer PASSWORD DISABLE;
   GRANT CREATE, TEMPORARY ON DATABASE <your_database> TO outdoo_writer;

The CREATE privilege lets Outdoo create schemas/tables, and TEMPORARY allows usage of temp tables during loads. If you prefer not to use IAM auth, you can set a password and provide it to Outdoo securely, though IAM roles are more secure.

Whitelist Outdoo's IP (if needed): If your Redshift is in a VPC with restricted access, add an inbound rule to its security group to allow connections from Outdoo. Allow Outdoo's static IP on the Redshift port (5439 by default).

Set Up an S3 Staging Bucket: Create an S3 bucket for staging data files during the load process (for example, my-company-outdoo-stage). Place the bucket in the same AWS region as your Redshift cluster for best performance.

Create an IAM Role for Outdoo: In AWS IAM, create a role that Outdoo's service can assume. Set up a trust policy on this role to trust Outdoo's AWS account (Outdoo will provide their AWS Account ID and an external ID or role ARN). Attach a permissions policy to this role that allows:

S3 Access: s3:PutObject, GetObject, DeleteObject on the staging bucket, and ListBucket on the bucket itself

Redshift Credentials: redshift:GetClusterCredentials for the Redshift cluster, user, and database that Outdoo will use

Share Connection Details with Outdoo: In the Outdoo setup interface for Redshift integration, provide the Redshift cluster endpoint (host and port), database name, the DB user (outdoo_writer), the target schema name (for example, outdoo_data), the S3 bucket name, and the IAM Role ARN.

Outdoo Data Loading Process: Once configured, Outdoo will connect to your Redshift using the IAM role. For each sync batch, Outdoo extracts new or updated data, writes it to files in the S3 staging bucket, then issues a Redshift COPY command to load the data from S3 into the target table. Call data is pushed shortly after each call is analyzed. Deal data is pushed on a scheduled interval (for example, nightly).

Validation: Check your Redshift cluster for the new schema and tables after the first sync. Run SELECT COUNT(*) FROM outdoo_data.calls; to see the number of call records.

Data Schema and Table Design

The analyzed Outdoo data is structured in a star schema format centered around two fact tables: Calls and Deals.

Calls Table: Each row represents a single sales call or meeting. Key fields include call_id, call_timestamp, duration_seconds, participant identifiers, and analysis results such as sentiment_score, talk_ratio_percent, interactions_count, and keywords or topics detected. Transcripts may be stored as a separate table (call_transcripts) keyed by call_id.

Deals Table: Each row represents a sales opportunity. Fields include deal_id, deal_name, owner, account_name, stage, amount, close_date, last_call_date, and AI-generated metrics such as deal_health_score. There may also be a deal_history or deal_stage_history table capturing stage changes over time.

Additional Tables: Depending on your Outdoo package, you may also have tables for users/employees, accounts, call metrics or topics, and deal forecast/scoring.

All tables include an updated_at timestamp and an is_deleted flag for soft-deleted records. Use these to manage incremental models or filter active records.

With Outdoo data in Redshift, your BI team can use tools like Amazon QuickSight or Tableau to create unified dashboards combining Outdoo's call sentiment and talk-time metrics with your sales pipeline data.

Integration with Snowflake

Integration with Databricks

Outdoo Open API