Source and destination reference
Every source Intempt can read from and every destination it can write to: 12 of each, with what each one carries and how delivery is metered.
Overview
Intempt reads from sources and writes to destinations. This page lists every one of both, including those that do not yet have a Connect button in the console.
For how to connect one, see Sources, Destinations and the Integration catalog. This page is what exists, not how to wire it.
Sources
Each source provisions its own event collections when connected. Which ones, and every attribute on them, is in Event reference and Event taxonomy.
| Source | Type key | Kind | Provisioned collections |
|---|---|---|---|
| Web (JavaScript) | web | SDK | the web_* set |
| iOS | ios | SDK | the ios_* set |
| Android | android | SDK | named records, no android_* event set |
| React Native | react_native | SDK | none of its own |
| Node.js | nodejs | Server SDK | none of its own |
| PHP | php | Server SDK | none of its own |
| Python | python | Server SDK | none of its own |
| HTTP API | api | Direct | none — you define the events |
| Shopify | shopify | Platform | the shopify_* set |
| Stripe | stripe | Platform | the stripe_* set |
| HubSpot | hubspot | Platform | the hubspot_* set |
📘 "No provisioned collections" is not "cannot send events"
React Native, Node.js, PHP, Python and the HTTP API all send events through the same ingestion endpoint. They simply have no pre-defined collection set, so their events land in collections you define. Web, iOS, Shopify, Stripe and HubSpot arrive with a shape already agreed.
Destinations
Twelve destination types. The journey node column is the block you place on a journey canvas to reach that destination.
Messaging
| Destination | Type key | Journey node | Carries |
|---|---|---|---|
| SendGrid | sendgrid | send-email | |
| Intempt SES | intempt_ses | — | Bundled email. Created automatically, nothing to connect |
| Amazon SES | ses_email | send-ses-email | Email through your own verified SES domain |
| Gmail | gmail | gmail-email | Email, through a connected Google Workspace account |
| Twilio | twilio | send-sms | SMS |
| Firebase Cloud Messaging | firebase_cloud_messaging | send-push-notification | Mobile push |
| Slack | slack | slack | A message to a channel or user |
Data and systems
| Destination | Type key | Journey node | Carries |
|---|---|---|---|
| Kafka | kafka | kafka-publish | Enriched records onto a topic you own |
| Amazon S3 | s3 | s3-export | Enriched records written to a bucket you own |
| Webhook | webhook | webhook | An HTTP POST to any endpoint |
| HubSpot | hubspot | — | Write-back to HubSpot. Reached through Workflows, not journeys |
| Freshdesk | freshdesk | send-ticket | A support ticket |
📘 Two destinations have no journey node, for two different reasons
Intempt SES is bundled email. It is a system destination: isSystem is true and it is created for every project automatically, with no integration to connect and nothing to configure. It is the sender used when you have not brought your own. Bring your own domain and you are using ses_email instead, which is a destination you connect and which does have a journey node.
HubSpot write-back is locked to Workflows. Its three actions — create a task, update a property, add to a list — are workflow actions, not journey blocks. Pushing data back to HubSpot is done from a workflow. Everything else in both tables is reachable as a journey block.
Delivery modes
The two data destinations differ in when records arrive, not in what they contain.
| Mode | Destination | When records arrive |
|---|---|---|
| Streaming | Kafka | Each event is published as it happens |
| Batch | S3 | The same events, written on a window |
Both count the same unit — events delivered. The delivery mode sets the rate, not what is counted, so the same event costs differently depending on how quickly you need it. You choose per destination, which means you can stream to the topic your systems watch and batch to the bucket your warehouse reads.
Messaging destinations are metered per send, per channel: email, SMS and push are counted separately.
Use cases
- Confirm a destination exists, and that it has a journey node, before designing a journey around it. Kafka is connected from the Add Integration panel and published to from a workflow, not a journey block. See Apache Kafka.
- Check whether a source provisions collections before planning a tracking plan; an API or React Native source needs you to define events first.
- Pick a delivery mode per destination rather than for the whole account, so latency is paid for only where it is needed.
- Look up the journey node name when building a journey through the API rather than the canvas.
Where to go next
HubSpot record taxonomy
Every field on every HubSpot record, nested ones included, with the type it carries and whether it is required.
Customer Profile Schema Reference
Every user's profile is a record built from identity fields, system fields, and attributes. This reference lists every field on that record and what it means.