Webhooks: connect your CRM to Slack, Teams, Make and n8n without a native app

With workflows and webhooks, Advanzo reports every important change to the tool your team already works in: a won deal appears in Slack or Teams, a new lead starts a scenario in Make or n8n, Zapier adds a row to your spreadsheet. You need no native app and no programming. One rule, one URL, done. In the other direction, the REST API works with personal access tokens.

This article is for teams of 2 to 50 people who use Advanzo as their sales CRM and whose working day happens in Slack, Microsoft Teams or an automation tool such as Make, n8n or Zapier. It explains what a webhook is, how you fire one from Advanzo and where the limits are.

The problem today: what happens in the CRM stays in the CRM

A deal is won. The person who closed it knows. Everyone else finds out at the Monday meeting, or not at all. Accounting waits for an email, the project team only creates the folder when someone asks. The information exists in the CRM, but it never arrives where the work happens.

Many teams solve this by hand: whoever wins a deal writes a message in the Slack channel. Whoever creates a new lead copies it into the marketing spreadsheet. That works as long as everyone remembers. After three weeks, nobody remembers.

The second solution is native integrations from a marketplace. The large CRM vendors have hundreds of them, often with their own price tag and their own configuration per tool. For a small team that is too much weight for a goal you can describe in one sentence: "When X happens, tell channel Y." That is exactly what webhooks are for.

What a webhook is, and what it is not

A webhook is a message that one system sends to a URL as soon as an event occurs. Technically it is an HTTP POST with a data packet in JSON format, the so-called payload. The receiver is a service waiting for messages at that URL: a Slack channel, a Teams channel, a scenario in Make, a workflow in n8n, a Zap in Zapier.

The difference from an API query: with a webhook, Advanzo speaks up by itself, at the moment of the event. Nobody has to ask every five minutes whether anything has changed. The difference from a native app: there is no marketplace, no installation and no permission prompt. You give Advanzo a URL, and Advanzo sends to it.

What the payload contains depends on the trigger. These parts are typical:

The receiver decides what to do with this information. Slack shows a message. Make or n8n can create a folder, prepare an invoice or write a row into a sheet. Advanzo only sends. What happens next is decided by your scenario in the receiving tool.

Step by step: a won deal lands in the Slack channel

Workflows in Advanzo follow one pattern: when a record is created or a field changes, then an action happens. Possible actions are creating an activity, sending an email or firing a webhook. Advanzo ships with templates, among them the classics "deal won, notify channel" and "new lead, create task". The example here shows the route to Slack. For Microsoft Teams the process is identical, only the URL comes from Teams.

Step 1: Create an incoming webhook in Slack

In Slack, under the app settings, you create an "Incoming Webhook" for the channel, for example #sales-wins. Slack generates a URL for it. Copy it. This URL is the only thing Advanzo needs to know. In Microsoft Teams the feature is also called "Incoming Webhook" and is set up per channel.

Step 2: Create the workflow in Advanzo

1. Open workflows and choose the "deal won" template, or start from scratch.
2. Trigger: the "stage" field of a deal changes to "Won".
3. Give the workflow a name the team understands, such as "Won, then #sales-wins".

Step 3: Choose the "webhook" action and paste the URL

As the action you choose "fire webhook" and paste the Slack URL. On every match, Advanzo sends the payload to that address. If you also want a task "start onboarding" for the deal owner, create a second rule with the same trigger and the action "create activity".

Step 4: Test with a test deal

1. Create a deal called "Test webhook" and move it to "Won".
2. Check whether the message appears in the channel.
3. Nothing appears: check the URL, check the trigger, move the test deal again.

Step 5: Activate the workflow and tell the team

Activate the workflow and tell the team in one sentence what happens now: "Every won deal appears automatically in #sales-wins, you no longer need to post anything." Delete the test deal or mark it lost with the reason "test".

Step 6: More rules on the same pattern

From here the pattern repeats. New contact from a web form: webhook to Make, which triggers a welcome in your mail tool. Lost reason set to "price": message to the management channel. New deal in the "major projects" pipeline: task "plan kick-off" for the head of sales. How to keep such rules small and prioritise them is covered in automate repetitive sales tasks.

Slack, Teams, Make, n8n, Zapier: who receives what

One clear statement first: Advanzo has no native Slack app and no native Zapier app. There is no listing in their marketplaces that you could install. The connection always runs through webhooks from workflows. That sounds like less, but in practice it is often more, because you are not tied to the fields a ready-made app provides.

Make, n8n and Zapier act as distributors: a webhook from Advanzo starts a scenario there that branches as far as you like. That is how you reach tools for which there will never be a native CRM app. Which connections pay off first for a sales team is in integrations every sales team should set up.

The other direction: REST API with personal tokens

Webhooks flow out of Advanzo. When data needs to flow in, you use the REST API. It covers every resource: contacts, companies, deals, activities, products, documents. Access runs through personal access tokens that each person creates in their profile. A token belongs to one person and to their permissions. What the person cannot see, their token cannot see either.

Three typical cases: a Make scenario creates a contact in Advanzo when someone opens a ticket in the support tool. An n8n workflow fetches every morning all deals with a close date this week and posts the total in Teams. A script imports product prices from a spreadsheet into the product catalogue once a month. Credentials and tokens are encrypted in transit and at rest, and the audit log shows who changed what and when.

Checklist before your first webhook

• The event is written in one sentence: "When a deal is won, then message to #sales-wins."
• The receiver is decided and the webhook URL has been generated.
• The URL is treated like a password: not shared in chat, not stored in a spreadsheet.
• The trigger is as narrow as possible: the one field, the one value.
• One person owns the workflow and is named in the rule.
• A test deal exists and the test is documented.
• The team knows the message now arrives automatically and nobody needs to post manually.
• For Make, n8n or Zapier, the scenario is built so that a duplicate webhook does not create a duplicate record.

Mini scenario: logistics company with 12 people in Basel

Rhein Logistik AG has four people in sales, five in dispatch and three in administration. The team works in Microsoft Teams. Until now, sales wrote a message in the "New orders" channel after every close so that dispatch could plan. In one quarter with 38 won deals, seven messages were missing and two orders started a week late.

The fix took one hour: an incoming webhook in the Teams channel, a workflow "stage changes to Won, then webhook" in Advanzo, plus a second rule that creates a task "plan kick-off" for the head of sales on the same trigger. Since then every close appears in the channel within seconds, with customer, value and delivery date.

Typical mistakes with webhooks and workflows

• Trigger too broad: "when a deal changes" fires on every note and every date. After a day the team mutes the channel. Choose the field and the value that matter.
• The URL as common property: anyone who knows the webhook URL can post messages into the channel. Treat it like a password and regenerate it when someone leaves the team.
• No test: the workflow is activated and "will probably work". At the first real close the message is missing and nobody notices. A test deal costs two minutes.
• Logic in the CRM instead of the distributor: if you have five targets, do not build five workflows. One webhook to Make or n8n, distribution there.
• Expecting a native app: there is no Advanzo listing in the Slack directory. Whoever searches for it searches in vain. The route is the channel's incoming webhook.
• Automating before documenting: if nobody can say what should happen after a won deal, no webhook will help. Write the process down first, then the rule. More on that in document your sales process before automating.

Frequently asked questions

Does Advanzo have a Slack app or a Zapier app?

No. There is no listing in the Slack directory and none in Zapier. The connection runs through webhooks from workflows: you create an incoming webhook in Slack, a "Catch Hook" in Zapier, and enter the URL in Advanzo. For the other direction, the REST API is available.

Which events can fire a webhook?

A workflow starts when a record is created or a field changes. That applies to contacts, companies, deals and activities. You choose the field and the value, such as stage equals "Won" or lost reason equals "price". The action can be a webhook, an activity or an email.

Do I need programming skills?

For Slack and Teams, no: copy the URL, paste it into the workflow, test. For Make, n8n and Zapier you build a scenario in that tool, which works by clicking, without code. Only if you address the REST API directly do you write a script or use the HTTP module of your automation tool.

Can I write data into Advanzo from outside?

Yes, through the REST API with personal access tokens. It covers all resources: contacts, companies, deals, activities, products and documents. Every token is tied to one person and their permissions. Credentials and tokens are encrypted in transit and at rest.

What is the difference between a webhook and an API?

A webhook pushes: Advanzo contacts the receiver as soon as something happens. An API pulls or writes: your tool asks Advanzo for data or creates some, whenever it wants. In practice you often need both, for example a webhook as the starting signal and an API call that then completes the record.

If you want to try this in Advanzo: advanzo.app.