17 docs tagged with "SQL"

This page covers advanced scenarios for the Account model. Each section explains a specific configuration goal, how it works in FunnelStory, and provides query examples for multiple data source types.

The Amazon Athena connection lets FunnelStory run queries in your AWS account against data in S3 via Athena, so data models can use curated tables in the AWS Glue Data Catalog (or supported catalogs).

The Amazon Redshift connection lets FunnelStory query your Redshift cluster or Serverless workgroup with read-only SQL to power data models—often used for warehouse-native account and revenue facts.

The Attio connection lets FunnelStory read CRM objects from your Attio workspace so you can configure data models using Attio’s API-shaped AT blocks (filter, sort, and object type) in the model query step.

FunnelStory exposes four tools through the MCP server.

The BigQuery connection uses a Google service account so FunnelStory can run read-only jobs against your datasets and drive data models from BigQuery tables and views.

The Databricks connection lets FunnelStory run SQL against Databricks SQL warehouses (or SQL endpoints) so data models can read from Unity Catalog–backed tables and views your team already curates.

The HubSpot connection links FunnelStory to your HubSpot portal via OAuth so you can build data models on companies, deals, and contacts using HubSpot’s search APIs (HS blocks in the query step), power CRM sync, and use HubSpot in workflows or analytics where enabled.

The Microsoft SQL Server connection lets FunnelStory run read-only queries against SQL Server (or Azure SQL where supported) to back data models such as accounts, contracts, and usage summaries.

The MySQL connection lets FunnelStory run read-only SQL against your MySQL database to power data models—accounts, users, billing tables, or any view you maintain for analytics.

The PostgreSQL connection lets FunnelStory run read-only SQL against your database to power data models (for example accounts, users, subscriptions, and warehouse-backed metrics). Use it when your source of truth already lives in Postgres or when you expose reporting views for FunnelStory to query.

Before configuring the Account model, you need at least one data connection in FunnelStory. A data connection is a link between FunnelStory and an external system that holds your account data.

This page provides complete, end-to-end Account model configurations for common setups. Each example includes the full query, the property mapping table, and an explanation of what's being configured.

The Salesforce connection authorizes FunnelStory to read your CRM data using OAuth. Use it to back data models (with SOQL in the model builder), to support CRM sync where your workspace writes selected fields back to Salesforce, and anywhere else the product surfaces Salesforce as a source.

The Snowflake connection lets FunnelStory query your warehouse with read-only access so you can build data models on curated tables and views—common for ARR, account dimensions, and historical metrics.

Steps pass data through variables. Templates turn those values into SQL, JSON arguments, and prompts.

The query you write determines what data FunnelStory pulls into the Account model. The format depends on your data source type. This page covers the query syntax for every supported connection type.