How to connect Google Cloud Pub\Sub and Lexoffice
Create a New Scenario to Connect Google Cloud Pub\Sub 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 Cloud Pub\Sub, triggered by another scenario, or executed manually (for testing purposes). In most cases, Google Cloud Pub\Sub or Lexoffice will be your first step. To do this, click "Choose an app," find Google Cloud Pub\Sub or Lexoffice, and select the appropriate trigger to start the scenario.

Add the Google Cloud Pub\Sub Node
Select the Google Cloud Pub\Sub node from the app selection panel on the right.


Google Cloud Pub\Sub

Configure the Google Cloud Pub\Sub
Click on the Google Cloud Pub\Sub node to configure it. You can modify the Google Cloud Pub\Sub 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 Cloud Pub\Sub node, select Lexoffice from the list of available apps, and choose the action you need from the list of nodes within Lexoffice.


Google Cloud Pub\Sub
⚙

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 Cloud Pub\Sub 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 Cloud Pub\Sub 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 Cloud Pub\Sub
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Google Cloud Pub\Sub, 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 Cloud Pub\Sub and Lexoffice integration works as expected. Depending on your setup, data should flow between Google Cloud Pub\Sub 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 Cloud Pub\Sub and Lexoffice
Google Cloud Pub/Sub + Lexoffice + Slack: While a direct Pub/Sub trigger is unavailable, this use case cannot be fully implemented as initially described. However, upon manual data entry into Lexoffice, specifically when a new voucher is created, a notification will be sent to a designated Slack channel informing the accounting team. This will act as a reminder to check for new sales data potentially sourced from external systems using Pub/Sub.
Lexoffice + Google Cloud Pub/Sub + Google Sheets: When a new voucher is created in Lexoffice, the details will be added as a new row to a Google Sheet. While direct Pub/Sub trigger functionality isn't available, this setup allows manual integration of external Pub/Sub data into Lexoffice. This setup facilitates tracking and reporting on invoice payments.
Google Cloud Pub\Sub and Lexoffice integration alternatives

About Google Cloud Pub\Sub
undefined
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 Cloud Pub\Sub and Lexoffice
How can I connect my Google Cloud Pub\Sub account to Lexoffice using Latenode?
To connect your Google Cloud Pub\Sub account to Lexoffice on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Cloud Pub\Sub and click on "Connect".
- Authenticate your Google Cloud Pub\Sub and Lexoffice accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Lexoffice invoices from Pub\Sub messages?
Yes, you can. Latenode's visual editor simplifies the process, letting you map data from Pub\Sub directly into Lexoffice invoices. Automate accounting and save time with real-time message processing.
What types of tasks can I perform by integrating Google Cloud Pub\Sub with Lexoffice?
Integrating Google Cloud Pub\Sub with Lexoffice allows you to perform various tasks, including:
- Triggering invoice creation in Lexoffice from specific Pub\Sub messages.
- Updating customer details in Lexoffice based on data from Pub\Sub topics.
- Logging Pub\Sub message data to Lexoffice as journal entries.
- Automatically sending payment reminders from Lexoffice via Pub\Sub messages.
- Creating new Lexoffice contacts from incoming Pub\Sub data streams.
How does Latenode handle authentication with Google Cloud Pub\Sub?
Latenode uses secure OAuth 2.0 to authenticate your Google Cloud Pub\Sub account, ensuring safe access to your data without storing credentials.
Are there any limitations to the Google Cloud Pub\Sub and Lexoffice integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require JavaScript code blocks.
- Real-time message processing depends on the Pub\Sub message volume.
- Custom Lexoffice fields require careful data mapping in Latenode.