This template watches a Snowflake table for new rows, maps click id, conversion time, and value in JavaScript, and sends an offline conversion to Google Ads.
Connect Snowflake and Google Ads. Point the trigger at the table that stores conversions. Keep Snowflake credentials on the Snowflake connection and Google Ads on the Google Ads connection.
Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.
Full pricing — how CPU seconds work →Workflow preview
The scenario starts when a new row is added to the Snowflake table you choose.
JavaScript maps click id, conversion time, value, and currency into the fields Google Ads expects.
Google Ads records the offline conversion on the conversion action you select.
Add a Snowflake connection with access to the warehouse, database, and table that stores conversions. Watch new rows on that table.
Add a Google Ads connection for the account that should receive offline conversions.
In JavaScript, map Snowflake columns to click id, conversion time, value, and currency. Send the offline conversion in Google Ads. Insert a test row and confirm it appears in Google Ads.
FAQ
More templates
This template runs on a schedule, opens each URL in a headless browser, and compares visible text to the last snapshot in Latenode Database. When the change crosses your threshold, JavaScript builds RSS XML and Google Drive saves the feed file. Connect Google Drive. Keep snapshots in Latenode Database keyed by URL.
This template receives Cognito Forms submissions on a Latenode webhook, maps the payload, then creates or updates the contact in ActiveCampaign and applies a tag. Paste the webhook URL into Cognito Forms. Connect ActiveCampaign and put the API URL and key on that connection. Map email so matches update the same person.
This template watches a Discord channel for new messages, translates the text with Google Cloud Translate, and posts the translation back to Discord. Connect a Discord bot and Google Cloud Translate. Put the Translate API key on the Google Cloud Translate connection. Point the trigger at the channel you want to translate and pick the target language.
