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

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


Lexoffice

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


Lexoffice
⚙
TickTick

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

Lexoffice
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Lexoffice, TickTick, 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 Lexoffice and TickTick integration works as expected. Depending on your setup, data should flow between Lexoffice and TickTick (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Lexoffice and TickTick
Lexoffice + TickTick + Slack: When an invoice in Lexoffice is overdue (simulated by listing invoices), a task is created in TickTick to follow up on the payment. A message is sent to a Slack channel to alert the finance team.
TickTick + Lexoffice + Google Sheets: When a tax-related task is completed in TickTick, the completion status is added to a Google Sheet. Unfortunately, sending receipts in Lexoffice based on this is not possible due to missing Lexoffice triggers, so the automation only updates the spreadsheet.
Lexoffice and TickTick integration alternatives

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
About TickTick
Use TickTick within Latenode to automate task creation from various triggers like new form submissions or database entries. Keep projects on track by automatically generating tasks and subtasks, assigning due dates, and sending reminders. Integrate TickTick with other apps for a streamlined workflow—avoid manual task management and improve team productivity.
Related categories
See how Latenode works
FAQ Lexoffice and TickTick
How can I connect my Lexoffice account to TickTick using Latenode?
To connect your Lexoffice account to TickTick on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Lexoffice and click on "Connect".
- Authenticate your Lexoffice and TickTick accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create tasks from new Lexoffice invoices?
Yes, you can! Latenode allows seamless automation, turning new invoices into actionable TickTick tasks, ensuring timely follow-up and improved financial task management.
What types of tasks can I perform by integrating Lexoffice with TickTick?
Integrating Lexoffice with TickTick allows you to perform various tasks, including:
- Create a task in TickTick for each new Lexoffice invoice.
- Update task status in TickTick when an invoice is paid.
- Send payment reminders from TickTick based on Lexoffice data.
- Create recurring tasks for monthly Lexoffice reports.
- Synchronize contact details between Lexoffice and TickTick.
Can I filter Lexoffice invoices by status in Latenode?
Yes, use Latenode's data filters and Javascript blocks to process only invoices matching specific criteria, maximizing workflow relevance and efficiency.
Are there any limitations to the Lexoffice and TickTick integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations might require JavaScript knowledge.
- Real-time synchronization depends on the API availability of both apps.
- Initial setup requires understanding of both Lexoffice and TickTick data structures.