Get started with a free trial today
Already have an account? Sign in
Stitch’s Crossbeam integration replicates data using theCrossbeam API. Refer to theSchema section for a list of objects available for replication.
A high-level look at Stitch's Crossbeam (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status | Beta | Supported by | |
| Stitch plan | Standard | API availability | Available |
| Singer GitHub repository | |||
| REPLICATION SETTINGS | |||
| Anchor Scheduling | Supported | Advanced Scheduling | Supported |
| Table-level reset | Unsupported | Configurable Replication Methods | Unsupported |
| DATA SELECTION | |||
| Table selection | Supported | Column selection | Supported |
| Select all | Supported | ||
| TRANSPARENCY | |||
| Extraction Logs | Supported | Loading Reports | Supported |
To set up Crossbeam in Stitch, you need:
A Crossbeam application. For information on how to create one, see Crossbeam’sDeveloper Docs.
On the Stitch Dashboard page, click theAdd Integration button.
Click theCrossbeam icon.
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Crossbeam” would create a schema calledstitch_crossbeam in the destination.Note: Schema names cannot be changed after you save the integration.
The Sync Historical Data setting defines the starting date for your Crossbeam integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Crossbeam’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.
In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Crossbeam integrations support the following replication scheduling methods:
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.
The last step is to select the tables and columns you want to replicate.Learn about the available tables for this integration.
Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.
For Crossbeam integrations, you can select:
Individual tables and columns
All tables and columns
Click the tabs to view instructions for each selection method.
To track a table, click thecheckbox next to the table’s name. A blue checkmark means the table is set to replicate.
To track a column, click thecheckbox next to the column’s name. A blue checkmark means the column is set to replicate.
Click theTables to Replicate tab.
In the menu that displays, clickTrack all Tables and Fields:

After you finish setting up Crossbeam, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to theAnchor Scheduling documentation for more information.
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is forversion 1 of this integration.
This is the latest version of the Crossbeam integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs >customers), while case is maintained in PostgreSQL destinations (CusTomERs >CusTomERs). Refer to theLoading Guide for your destination for more info.
Thepartner_populations table contains information about the populations that your partners have shared with you in your Crossbeam account.
Full Table | |
Primary Key | id |
| Useful links |
id INTEGER |
name STRING |
organization_id INTEGER |
population_type STRING |
Thepartners table contains information about your partners as well as partner invitations sent to you in your Crossbeam account.
Full Table | |
Primary Key | id |
| Useful links |
clearbit_domain STRING | ||||
domain STRING | ||||
id INTEGER | ||||
logo_url STRING | ||||
name STRING | ||||
url STRING | ||||
users ARRAY
| ||||
uuid STRING |
Thepopulations table contains information about all of your populations in your Crossbeam account.
Full Table | |
Primary Key | id |
| Useful links |
base_schema STRING | |||||||
base_table STRING | |||||||
current_version OBJECT
| |||||||
filter_expression ARRAY | |||||||
filter_parts ARRAY
| |||||||
id INTEGER | |||||||
name STRING | |||||||
population_type STRING | |||||||
source_id INTEGER |
Thethread_timelines table contains information about the activity for any giventhread-id in your Crossbeam account. This is a child table ofthreads.
Full Table | |
Primary Key | id |
| Useful links |
acting_organization_id INTEGER | ||||
created_at DATE-TIME | ||||
event_data OBJECT
| ||||
event_type STRING | ||||
id STRING | ||||
is_private BOOLEAN | ||||
message OBJECT
|
Thethreads table contains information about all threads initiated by you in your Crossbeam account.
Full Table | |
Primary Key | id |
| Useful links |
author_id INTEGER |
company_domain STRING |
company_name STRING |
created_at DATE-TIME |
directionality STRING |
id STRING |
is_open BOOLEAN |
is_unread BOOLEAN |
last_comment_at DATE-TIME |
last_viewed_at DATE-TIME |
organization_id INTEGER |
owner_id INTEGER |
partner_organization_id INTEGER |
partner_owner_id INTEGER |
person_email STRING |
record_id STRING |
source_id INTEGER |
title STRING |
total_messages INTEGER |
updated_at DATE-TIME |
| Related | Troubleshooting |
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.