How to connect Google Ads and SendPulse
Create a New Scenario to Connect Google Ads and SendPulse
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Google Ads, triggered by another scenario, or executed manually (for testing purposes). In most cases, Google Ads or SendPulse will be your first step. To do this, click "Choose an app," find Google Ads or SendPulse, and select the appropriate trigger to start the scenario.

Add the Google Ads Node
Select the Google Ads node from the app selection panel on the right.

Google Ads
Configure the Google Ads
Click on the Google Ads node to configure it. You can modify the Google Ads URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the SendPulse Node
Next, click the plus (+) icon on the Google Ads node, select SendPulse from the list of available apps, and choose the action you need from the list of nodes within SendPulse.

Google Ads
⚙

SendPulse

Authenticate SendPulse
Now, click the SendPulse node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your SendPulse settings. Authentication allows you to use SendPulse through Latenode.
Configure the Google Ads and SendPulse Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Google Ads and SendPulse Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙

SendPulse
Trigger on Webhook
⚙
Google Ads
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Google Ads, SendPulse, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Google Ads and SendPulse integration works as expected. Depending on your setup, data should flow between Google Ads and SendPulse (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google Ads and SendPulse
Google Ads + SendPulse + Facebook: When a contact is added to a Google Ads customer list, they are added to a SendPulse mailing list. This list can then be used to create a lookalike audience on Facebook for targeted advertising (note: direct Facebook lookalike audience creation is unavailable, this step would need manual setup in Facebook).
SendPulse + Google Ads + Zoho CRM: When a new subscriber event occurs in SendPulse, their email is used to add them to a Google Ads customer list for retargeting. The contact information is also used to create or update a lead in Zoho CRM.
Google Ads and SendPulse integration alternatives
About Google Ads
Use Google Ads in Latenode to automate campaign management and reporting. Pull ad performance data, adjust bids based on real-time events, or trigger alerts for budget changes. Combine with other apps to build custom marketing workflows. Latenode's flexibility avoids rigid, pre-built integrations and costly per-step pricing.
Similar apps
Related categories

About SendPulse
Use SendPulse in Latenode for automated email & SMS marketing. Trigger campaigns based on real-time events, segment contacts dynamically, and personalize messages using data from any app. Automate list cleaning and optimize send times in response to user behavior. Connect SendPulse to any data source for smarter, event-driven communication workflows.
Similar apps
Related categories
See how Latenode works
FAQ Google Ads and SendPulse
How can I connect my Google Ads account to SendPulse using Latenode?
To connect your Google Ads account to SendPulse on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Ads and click on "Connect".
- Authenticate your Google Ads and SendPulse accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically add leads from Google Ads to SendPulse?
Yes, you can! Latenode allows seamless lead synchronization. Automatically add new leads to SendPulse for targeted campaigns, enhancing follow-up and conversion rates.
What types of tasks can I perform by integrating Google Ads with SendPulse?
Integrating Google Ads with SendPulse allows you to perform various tasks, including:
- Automatically adding new Google Ads leads to a SendPulse mailing list.
- Triggering SMS campaigns in SendPulse based on Google Ads conversions.
- Updating contact information in SendPulse based on Google Ads data.
- Creating personalized email sequences based on Google Ads keywords.
- Sending alerts via SendPulse for high-performing Google Ads campaigns.
What kind of Google Ads data can I access in Latenode?
You can access campaign performance, ad group statistics, keyword data, conversion metrics, and cost information within Latenode for advanced automation.
Are there any limitations to the Google Ads and SendPulse integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Historical data migration might require custom scripting due to API limits.
- Complex audience segmentation in SendPulse needs careful data mapping.
- Real-time updates depend on Google Ads and SendPulse API availability.