Why use Zapier?
Zapier lets you connect ProductBet to 7,000+ apps without writing code. Route feedback from forms, CRMs, support tools, surveys, and more into your product signal pipeline automatically.
Getting started
- Go to Settings > Integrations > Zapier and click Generate API Key.
- Copy your API key and endpoint URL.
- In Zapier, search for ProductBet and select the Create Signal action.
- Enter your API key and endpoint URL when prompted.
- Choose a trigger app (e.g. Typeform, Google Forms, Zendesk) and map fields.
Available actions
Create Signal
Sends a product signal to ProductBet for AI-powered analysis.
#### Required fields
| Field | Description |
|---|---|
| Signal ID | Unique identifier for deduplication. Use a stable ID from your source (e.g. form submission ID). |
| Content | The text content to analyze. This is what the AI processes to extract insights. |
#### Optional fields
| Field | Description |
|---|---|
| Source URL | Link back to the original source. |
| Tags | Comma-separated tags to attach to the signal. |
| Signal Type | Override AI classification: feature_request, bug, support_ticket, deal_lost, deal_won, churn_signal |
| Sentiment | Override AI sentiment: positive, negative |
| Actor Type | Override AI actor: customer, prospect, churned_user, team_member, partner |
| Topic | Override AI topic: onboarding, core_workflow, reporting, integrations, search, notifications, admin, pricing, security, compliance, billing, support, competition, documentation, other |
| Summary | Override AI-generated summary. |
| Goal | Override AI-extracted goal. |
| Timestamp | Unix timestamp in milliseconds. Defaults to now. |
| Metadata (JSON) | Arbitrary JSON object stored with the signal. |
Example Zaps
- Typeform → ProductBet: Route survey responses as product signals.
- Zendesk → ProductBet: Send new support tickets as signals for pattern detection.
- Google Forms → ProductBet: Collect feature requests from a public form.
- HubSpot → ProductBet: Import deal notes when a deal is closed-lost.
Tips
- Use a unique, stable Signal ID per submission to avoid duplicates. Most Zapier triggers provide an ID field you can map.
- Leave classification fields blank to let ProductBet's AI classify automatically. Only override when your source system already knows the type.
- Use Tags to label signals by source (e.g. "typeform", "survey-q3") for easy filtering later.
Troubleshooting
- Signal not appearing? Check that the Signal ID is unique. Reusing the same ID updates the existing signal.
- Authentication error? Verify your API key starts with
pb_live_and your endpoint URL ends with/ingest. - Zap failing? Make sure Content is not empty — it's a required field.