Automation
Every company has steps someone does by hand simply because nobody has solved them yet: moving data between tools, chasing approvals, asking for status. We build those workflows in n8n, Make or Zapier — or directly against the API when ERP, CRM and accounting need to talk to each other. Including the exceptions off-the-shelf tools choke on.
Describe your workflow →Typical tasks
- Form → CRM + Slack notification
- Shopify order → Lexoffice invoice, with error handling
- Sync HubSpot ↔ Pipedrive
- Migrating from Zapier/Make to n8n (in several tasks)
Every task runs on your board in the Prozess-Abo: with acceptance criteria, delivered 48 hours after we start it — counted Mon 8 am to Fri 4 pm; over weekends and public holidays the clock stops. The first task is free. Scope per task in the service catalogue →
Example acceptance criteria
When we start a task, we record its acceptance criteria on the card. You measure acceptance against them — if a delivery doesn't meet them, we revise it at no extra cost until it does.
- 1The workflow runs 10 test cases without errors
- 2Failures are reported by email or Slack
- 3Credentials live in the credential store, not in the workflow
- 4Short documentation is included
What you get
- Recurring tasks run without anyone touching them
- No more maintaining the same record in several systems
- Error handling: the workflow tells you when something breaks
- Credentials stored as credentials, not inside the workflow
Technologies
n8n, Make, Zapier, REST, Webhooks, Lexoffice, HubSpot
Specific tasks
Describe your first task — it's free.
Create your workspace and put the task on your board. Before we start, we check that it fits into 48 hours (counted Mon 8 am – Fri 4 pm), and deliver it with acceptance criteria.