Onboarding Guide
Get up and running with Autobound Signal Data in under 30 minutes.
Welcome to Autobound Signal Data! This guide covers technical setup and working with our team.
Onboarding Timeline
| Week | Milestone |
|---|---|
| Week 1 | Kickoff call, credentials delivered, Slack Connect setup |
| Week 2 | First data pull, schema review, pipeline built |
| Week 3-4 | Signals matched to your records, first users enabled |
| Ongoing | Regular check-in calls as needed |
Onboarding Checklist
Team Setup
| Task |
|---|
| ☐ Join Slack Connect channel with Autobound |
| ☐ Schedule kickoff call (30 min) |
| ☐ Identify project team (see roles) |
Technical Setup
| Task | Resources |
|---|---|
| ☐ Receive and activate GCP credentials | Setup instructions |
| ☐ Verify bucket access | Delivery docs |
| ☐ Download first data file | Bucket structure |
| ☐ Parse and validate schema | Schema docs |
| ☐ Match signals to your records | Entity resolution |
Go-Live
| Task | Resources |
|---|---|
| ☐ Set up automated refresh pipeline | Delivery docs |
| ☐ Surface signals to end users | — |
| ☐ Schedule 30-day review call | — |
Who Should Be Involved
| Role | Responsibility |
|---|---|
| Data Engineer | Build ETL pipeline, manage GCS access |
| Product Manager | Define signal use cases, prioritize integration |
| Sales/Marketing Leadership | Validate data quality and fit for target use cases |
Kickoff attendees: Data Engineer + Product Manager recommended.
Working with Autobound
Slack Connect
Your shared channel is for:
- Quick questions (response within 4 hours)
- Data quality issues
- Schema clarifications
Success Sessions
30-minute check-ins, 2-3x per month for the first 1-2 months:
- Review pipeline progress
- Troubleshoot integration issues
- Optimize match rates
- Share best practices
After go-live, we move to monthly or as-needed.
Core Milestones
Week 1: Access & Kickoff
- Kickoff call completed
- Credentials received and tested
- Slack Connect active
Week 2: First Data Pull
- Downloaded data from at least one bucket
- Validated schema fields
- Initial pipeline created
Week 4: Review & Optimize
- Match rate calculated
- Signal taxonomy defined for your use case
- 30-day review scheduled
Technical Setup Details
Authentication
# Activate service account
gcloud auth activate-service-account --key-file=~/credentials/autobound-key.json
# Verify access by downloading from one of your licensed buckets
gcloud storage cp gs://autobound-10k/2026-01-15T00-00-00Z/output.parquet ./test-download.parquet
Note: Bucket listing is not supported. Use the direct bucket URLs from the Available Buckets section to verify access.
Bucket Structure
Each signal type has its own dedicated bucket with timestamped folders:
gs://autobound-{signal-type}/
├── 2026-01-05T12-00-00Z/ ← Most recent
│ ├── output.jsonl
│ └── output.parquetAlways pull from the most recent folder. See Delivery docs for details.
Available Buckets
Important: Bucket listing is not supported. Use the direct bucket URLs below to access your licensed signal types.
Company Signals:
| Signal Type | Bucket URL |
|---|---|
| SEC 10-K Filings | gs://autobound-10k/ |
| SEC 10-Q Filings | gs://autobound-10q/ |
| SEC 8-K Filings | gs://autobound-8k/ |
| SEC 20-F Filings | gs://autobound-20f/ |
| SEC 6-K Filings | gs://autobound-6k/ |
| Reddit (Company) | gs://autobound-reddit-company/ |
| Glassdoor Reviews | gs://autobound-glassdoor-company/ |
| LinkedIn Posts (Company) | gs://autobound-linkedin-post-company/ |
| YouTube (Company) | gs://autobound-youtube-company/ |
| X/Twitter (Company) | gs://autobound-x-company/ |
| GitHub Activity | gs://autobound-github/ |
| SEO Traffic | gs://autobound-seo-traffic/ |
| News Events | gs://autobound-news/ |
| Hiring Velocity | gs://autobound-hiring-velocity/ |
| Hiring Trends | gs://autobound-hiring-trends/ |
| Earnings Transcripts | gs://autobound-earnings-transcripts/ |
| Company Financials | gs://autobound-financials/ |
| Product Reviews | gs://autobound-product-reviews/ |
| Website Intelligence | gs://autobound-website-intelligence/ |
| Employee Growth | gs://autobound-employee-growth/ |
| Patents | gs://autobound-patents/ |
| Tech Used | gs://autobound-tech-used/ |
| Company Database | gs://autobound-company-database/ |
Contact Signals:
| Signal Type | Bucket URL |
|---|---|
| LinkedIn Posts (Contact) | gs://autobound-linkedin-post-contact/ |
| LinkedIn Comments (Contact) | gs://autobound-linkedin-comments-contact/ |
| X/Twitter (Contact) | gs://autobound-x-contact/ |
| YouTube (Contact) | gs://autobound-youtube-contact/ |
| Work Milestones | gs://autobound-work-milestones/ |
| Contact Database | gs://autobound-contact-database/ |
Download Data
# Download from a specific bucket (replace with your licensed bucket and timestamp)
gcloud storage cp gs://autobound-10k/2026-01-05T12-00-00Z/output.parquet ./
Tip: Your account manager will provide the specific bucket URLs and timestamps for your licensed data.
| Format | Best For |
|---|---|
| JSONL | Streaming, debugging |
| Parquet | Data warehouses, analytics |
Schema Overview
{
"signal_id": "uuid",
"signal_type": "10k",
"signal_subtype": "aiInvestment",
"detected_at": "2026-01-05T12:00:00Z",
"company": {
"name": "Acme Corp",
"domain": "acme.com"
},
"data": {
"summary": "...",
"relevance": 0.85
}
}Schema Overview
High-level schema structure
Full field reference: For complete field definitions, see the individual signal pages under Company Insights or Contact Insights.
Matching Signals
| Priority | Join Key |
|---|---|
| 1st | company.domain |
| 2nd | company.linkedin_url |
| 3rd | company.name (fuzzy) |
Entity Resolution
Best practices for matching
Key Documentation
| Resource | Link |
|---|---|
| Schema | /docs/schema |
| Entity Resolution | /docs/resolution |
| Delivery & Buckets | /docs/delivery |
| Signal Catalog | /docs/signal-catalog |
| Sample Files | /docs/files |
| Status & Known Issues | /docs/status |
| Roadmap | /docs/roadmap |
| Changelog | Changelog |
Updated 2 days ago