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

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

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

Memberstack
âš™

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 Memberstack 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 Memberstack 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
âš™
Memberstack
âš™
âš™
Iterator
âš™
Webhook response

Save and Activate the Scenario
After configuring Memberstack, 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 Memberstack and Lexoffice integration works as expected. Depending on your setup, data should flow between Memberstack 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 Memberstack and Lexoffice
Memberstack + Lexoffice + Slack: When a new member signs up in Memberstack, create a corresponding invoice in Lexoffice. Then, send a welcome message to the new member via Slack.
Lexoffice + Memberstack + Airtable: When a new invoice is created in Lexoffice, find the corresponding member in Memberstack and update their profile. Log the invoice and member data in Airtable for tracking and reporting.
Memberstack and Lexoffice integration alternatives
About Memberstack
Automate Memberstack user management with Latenode. Create workflows to onboard/offboard users based on triggers in other apps. Use webhooks to sync data, grant access, or update profiles. Connect Memberstack to CRMs, email tools, or databases for automated membership lifecycle management—all visually, without code, and at scale.
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.
Similar apps
Related categories
See how Latenode works
FAQ Memberstack and Lexoffice
How can I connect my Memberstack account to Lexoffice using Latenode?
To connect your Memberstack account to Lexoffice on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Memberstack and click on "Connect".
- Authenticate your Memberstack and Lexoffice accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automate invoice creation for new Memberstack members?
Yes, you can! Latenode lets you automatically trigger Lexoffice invoice creation when a new member joins Memberstack. This eliminates manual data entry and ensures timely billing, saving you time and reducing errors.
What types of tasks can I perform by integrating Memberstack with Lexoffice?
Integrating Memberstack with Lexoffice allows you to perform various tasks, including:
- Automatically creating invoices in Lexoffice for new Memberstack subscriptions.
- Updating member data in Lexoffice when changes occur in Memberstack.
- Sending automated payment reminders via Lexoffice based on Memberstack data.
- Generating financial reports using data from both Memberstack and Lexoffice.
- Managing subscription upgrades and downgrades within Lexoffice, triggered by Memberstack.
How do I handle errors when syncing Memberstack data to Lexoffice?
Latenode offers robust error handling, allowing you to define actions for failed data syncs, such as sending alerts or retrying the process automatically.
Are there any limitations to the Memberstack and Lexoffice integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Custom fields in Memberstack might require custom mapping configurations.
- High-volume data synchronization may be subject to API rate limits from either service.
- Complex discount structures might need additional logic within Latenode to be accurately reflected.