How to connect Google Ads and Lexoffice
Create a New Scenario to Connect Google Ads and Lexoffice
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 Lexoffice will be your first step. To do this, click "Choose an app," find Google Ads or Lexoffice, 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 Lexoffice Node
Next, click the plus (+) icon on the Google Ads node, select Lexoffice from the list of available apps, and choose the action you need from the list of nodes within Lexoffice.

Google Ads
⚙

Lexoffice

Authenticate Lexoffice
Now, click the Lexoffice node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Lexoffice settings. Authentication allows you to use Lexoffice through Latenode.
Configure the Google Ads and Lexoffice 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 Lexoffice 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
⚙

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

Save and Activate the Scenario
After configuring Google Ads, Lexoffice, 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 Lexoffice integration works as expected. Depending on your setup, data should flow between Google Ads and Lexoffice (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 Lexoffice
Google Ads + Lexoffice + Slack: When a Google Ads campaign reaches a certain spending threshold, the automation sends a notification to a designated Slack channel, prompting the finance team to review the budget within Lexoffice.
Google Ads + Lexoffice + Google Sheets: Retrieves advertising cost data from Google Ads. Then, the data is logged in Lexoffice, after which it is transferred to Google Sheets, adding a row for reporting and tracking purposes.
Google Ads and Lexoffice 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 Lexoffice
Automate accounting tasks by connecting Lexoffice to Latenode. Automatically create invoices, track expenses, or update customer data based on triggers from other apps. Latenode lets you build custom workflows around Lexoffice without code, adding features like advanced data validation or conditional logic that Lexoffice lacks natively.
Related categories
See how Latenode works
FAQ Google Ads and Lexoffice
How can I connect my Google Ads account to Lexoffice using Latenode?
To connect your Google Ads account to Lexoffice 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 Lexoffice accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I track ad spend against invoice data?
Yes, you can! Latenode's flexibility lets you build workflows to correlate Google Ads spend with Lexoffice invoice data. Optimize campaigns based on real financial performance and boost ROI.
What types of tasks can I perform by integrating Google Ads with Lexoffice?
Integrating Google Ads with Lexoffice allows you to perform various tasks, including:
- Automatically creating Lexoffice invoices for new Google Ads customers.
- Tracking Google Ads campaign costs against Lexoffice revenue data.
- Updating customer information in Lexoffice based on Google Ads conversions.
- Generating financial reports combining advertising and accounting data.
- Alerting teams of large discrepancies in ad spend versus generated revenue.
Can I use JavaScript code to transform data between Google Ads and Lexoffice?
Yes! Latenode allows you to use JavaScript blocks to transform data, enabling custom logic and data mapping between Google Ads and Lexoffice.
Are there any limitations to the Google Ads and Lexoffice integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Real-time data synchronization depends on the API rate limits of both services.
- Complex data transformations may require advanced JavaScript knowledge.
- Historical data import might require manual configuration due to API constraints.