Integration points

Integration points are pre-built journey elements for common third-party destinations, published by Pushwoosh as Point templates. Instead of building a raw Webhook request yourself, drag one onto the canvas from the Integrations section of the left panel and fill in its fields — Pushwoosh sends the request to the destination for you.

A template that reads its credential from your account’s 3rd-party integrations (like Google Sheets) needs that service connected first. A template that takes its own token as a field (like HubSpot and Airtable) needs no separate connection: configure the point and it’s ready to use.

Available Point templates

Google Sheets: add row

HubSpot: create or update contact

Airtable: create record

Configuring list and key/value fields

Point templates can take a variable number of values instead of a fixed set of fields. Depending on what the destination expects, a field takes one of two shapes:

• A list of values, for example Columns in Google Sheets: add row. Add a row for each additional value, and remove a row you no longer need. The order of your rows is what gets sent to the destination, for example the column order in the sheet. At least one row with a value is required, and a single blank row does not pass validation.
• A table of name/value pairs, for example Properties in HubSpot: create or update contact, or Fields in Airtable: create record. Add a row per property or field, with a name and its value. Names must be non-empty and unique within the table.

In either field, a row can hold a value from the current traveler instead of a fixed one, the same macros available in a Webhook body: {{device:hwid}}, {{device:user_id}}, {{tag:Name}}.

Note

If you configured one of these points before it supported a variable number of values (Google Sheets with fixed Column 1/Column 2/Column 3 fields, or HubSpot/Airtable with a single name/value pair), opening the point pre-fills your old values into the new field. Save the point once to move it onto the current template version — until you do, it keeps running with the version it was configured against.

Errors and failed requests

Every Point template on this page sends its request the same way as Webhook, with the same timeouts, retries, rate limits, and endpoint cooldown. A failed request drops the traveler from the journey at this step — see Request error.