Custom automations and integrations

We connect your tools so they work together and automate the processes you still do by hand.

When your software doesn't match the way you work, we adapt it. And that also means getting the different tools your business uses to work together.

We can connect your CRM, ERP, online stores, forms, databases, management tools or external services and build automations so information flows between them without manual work.

Diagnosis

When your applications don't talk to each other

Many businesses use good tools, but each one works on its own. The problem isn't always the software: it's all the work needed to move information from one system to another.

You copy information from one system to another

A customer fills in a form, someone enters the data into the CRM and then copies it again into another application. We can automate that journey.

Your ERP and your website work separately

We can connect your online store, website or internal apps with systems like SAP, Navision, Sage, Odoo or other ERPs, including in-house systems.

One action should trigger others

For example: New lead in Pipedrive → create record in Airtable → notify the sales rep → create a follow-up task.

One action can kick off a whole process without anyone having to step in at every stage.

You have too many repetitive tasks

Transferring information, creating records, sending alerts, updating statuses or starting processes are tasks that can often be automated.

Your Make or Zapier automation has become too small

We can review what you already have, optimise it, migrate it to another platform, or build the missing piece. You don't always need to start from scratch.

Integrations

We connect the tools you already use

You don't need to change the tools that work well for your business. We can look at how to connect them to each other and integrate them with your existing systems.

Do you use a different tool? No problem. If it has an API or some mechanism for exchanging information, we can most likely integrate it.

CRM

Pipedrive · Salesforce · HubSpot · other CRMs

ERP and business management

SAP · Navision · Sage · Odoo · Holded · in-house systems

Databases and management

Airtable · Monday · Notion · Google Sheets

Ecommerce

WooCommerce · Shopify · in-house platforms

Communication

Gmail · Outlook · WhatsApp Business · Telegram · Slack

Forms and lead capture

Typeform · Jotform · web forms · in-house forms

Payments and external services

Stripe · PayPal · external APIs · in-house services

Calendars

Google Calendar · Outlook Calendar · other systems

Platforms

Automations with n8n, Make, Zapier and Dify

We use different automation platforms depending on each project's needs. And when none fits completely, we can combine these tools with in-house development.

We don't work for a single tool. We choose whichever one best fits the problem.

n8n

An especially interesting option for flexible automations, complex flows and integrations that need more control. It can also be self-hosted on your own infrastructure.

Make

A very useful tool for quickly building visual flows between multiple applications and services.

Zapier

A good option for simple automations and direct connections between common services.

Dify

For when the automation needs to bring in artificial intelligence: interpreting information, working with a knowledge base, classifying content or using agents.

No-code

Automation without code… when it makes sense

Many integrations can be solved using tools like n8n, Make or Zapier, without needing to build everything from scratch.

And that's great when it's the right solution, but it isn't always, because some integrations need to:

  • Connect to APIs that don't offer exactly what we need.
  • Implement specific business logic.
  • Work with legacy or proprietary systems.
  • Perform complex validations.
  • Meet special security requirements.
  • Run custom code.
  • Communicate with applications built specifically for a business.

In those cases we can build the missing piece and combine it with the automation tools.

It's not about choosing between no-code or programming: it's about using each one where it adds the most value.

Artificial intelligence

We can also automate the intelligent part

An automation doesn't have to be limited to:

A happens → do B

It can also analyse information and decide what to do next:

A happens → analyse information → decide → run the corresponding process

For example:

Email received → Dify analyses it → identifies the type of request → n8n runs the corresponding flow → CRM updated

This makes it possible to automate processes that until recently needed a person to read, interpret and classify the information manually.

We can use artificial intelligence to:

  • Classify leads and requests.
  • Extract information from documents.
  • Analyse emails and forms.
  • Query an internal knowledge base.
  • Generate replies.
  • Identify the type of incident.
  • Decide which process should run.

AI doesn't necessarily replace the whole process. It can become one more piece within an automation.

Examples

Some examples of integrations

Every business has its own processes. Here are some examples of the kind of solutions we can build.

Pipedrive + internal systems + communication

Sales process automation, connecting the CRM with an internal database and communication tools.

A change in the CRM can automatically generate records, tasks, alerts or updates in other systems.

Airtable + ERP + WooCommerce

Syncing information between different systems to avoid entering and maintaining the same data in several places.

Data can flow between the online store, Airtable and the ERP according to the business's specific rules.

Dify + internal knowledge + WhatsApp

An AI-based system connected to the business's own information and to a communication channel like WhatsApp.

It can interpret queries, look up relevant information and take part in the support flow defined by the business.

Scope

What can we automate?

Practically any process that involves moving information between systems, applying certain rules or performing repetitive tasks can be a candidate for automation.

Sales

  • Lead capture and classification.
  • Automatic customer sign-up.
  • Sales follow-up.
  • CRM updates.
  • Creating tasks and alerts.

Administration

  • Invoice management.
  • Transferring information between systems.
  • Document generation.
  • Alerts and notifications.
  • Updating records.

Ecommerce

  • Product syncing.
  • Orders.
  • Stock.
  • Customers.
  • Shipping information.

Communication

  • Emails.
  • WhatsApp.
  • Telegram.
  • Internal notifications.
  • Automatic alerts to different teams.

Internal management

  • Forms.
  • Tasks.
  • Databases.
  • Updating information.
  • Approval workflows.

AI-driven processes

  • Classifying information.
  • Extracting data.
  • Analysing documents.
  • Processing emails.
  • Querying internal information.

Comparison

In-house development, n8n, Make, Zapier, …?

There's no single automation tool that's best for every project.

n8n — You need flexibility, complex flows or self-hosting.

Make — You want to build visual processes quickly.

Zapier — You need to connect common services simply.

Dify — You need to bring in AI, knowledge or agents.

In-house development — The integration requires specific logic or features.

And you don't need to pick just one, either.

An automation can use n8n to coordinate the process, Dify to interpret information and a custom-built API to communicate with an internal system.

The best solution can be a combination of several technologies.

Maintenance

An automation needs to be maintainable

Automating a process isn't just about getting it working today. You also need to think about what happens when tools change, connections fail, or the business's needs evolve.

What happens if it fails?

Processes can include logs, alerts, retries and mechanisms to detect errors and make them easier to fix.

What if an application changes?

APIs change, tools evolve, and businesses replace one system with another. We can adapt the integrations whenever necessary.

Who takes care of it afterwards?

We can help you maintain and evolve the automations so they keep working as your business changes.

FAQs

Frequently asked questions

How long does it take to set up an automation?

It depends on how complex the process is and which systems need to be connected. A simple automation can be ready quickly, while an integration with an ERP or an in-house system may need broader analysis and development.

Before we start, we can study the process and work out what it involves.

Can you automate a process we currently do manually?

Yes. In fact, you don't need to start from a specific automation idea.

We can analyse a process you currently do manually and look at which parts can be automated, which tools to use and what should stay under human control.

Can an automation be migrated from Zapier or Make to n8n?

In many cases, yes. First we need to analyse how the automation is built, what services it uses and what logic it contains.

It's not always worth migrating, but we can look at the case and assess the different options.

Can we host n8n on our own server?

Yes. n8n can be deployed on your own infrastructure, giving you more control over the environment the automations run in.

Whether it's worth doing depends on the project's technical, operational and security needs.

Can you connect systems without a public API?

It depends on the system and what options it offers for exchanging information.

Besides APIs, there can be other integration mechanisms, such as databases, files, webhooks or intermediate services. If there's no viable way to communicate, we'll look at what alternatives are possible.

What happens if an automation fails?

A well-designed automation needs to account for errors.

We can add execution logs, alerts, retries and mechanisms to detect when a process hasn't completed correctly.

What happens if we change the software we use?

Integrations may need adjustments when an application changes its API, changes how it works, or is replaced by another one.

We can take care of updating the automation to adapt it to the new scenario.

Do you need to write code to build an automation?

Not necessarily.

If n8n, Make, Zapier or any other tool solves the problem properly, we'll use that solution.

When an integration needs specific logic, features the platform doesn't offer, or communication with an in-house system, we can build the necessary part.

Where is the automation data stored?

It depends on the architecture chosen. We can work with cloud services or, when the project's needs justify it, use self-hosted solutions and your own servers.

The architecture is decided based on the systems used, the data processed, security and the business's needs.