Skip to main content

Incoming Webhook Type Problem

I've used incoming webhooks in the past to update existing contacts. After the FluentCRM 3.0 update, it looks like every incoming webhook has only one type for creating a new contact.

If I cannot update existing contacts with an incoming webhook, this creates a severe limitation for my workflows in n8n. Here's my example.

When a timer expires in a FluentCRM Automation, it sends an outbound webhook to n8n. Then n8n processes and returns a Pass or Fail value to FluentCRM via an incoming webhook.

I don't need to create a new contact, but that seems to be the only option. Why impose this limitation on how things communicate?

Is there an alternative I haven't considered? This sort of limitation is screwing up some client work I'm doing now. I appreciate any insight about this change and how to get around it.

Christian Frank

We use Flowmattic for inbound webhooks onto FCRM. The Create/Update action has worked well. Running inbounds from Vapi, Consolto and cross FComm->FCRM on different subdomains.

William Beem

Christian FrankΒ Thanks, I appreciate the input. I hate the idea that I'd have to tell my client to go buy a 3rd-party plugin to do something this product did out of the box before the latest version, though.

Since there is a Type field, it seems the solution is to add another type so it can work as before.

It's frustrating for me. This is a project I was going to complete today, and now I'm delayed. That means my payment for a few thousand dollars is potentially delayed, too.

William Beem

I have to do some testing, but I may have a way around this change. If FluentCRM updates an existing user (e.g., adds a tag or populates a custom field, that may suffice. I don't understand the purpose of creating a new field for Type and only having one type, though.

William Beem

Confirmed that FluentCRM will update an existing record rather than create a new one. I'll still say that this new field confused me and caused a delay from the previous webhooks I've created, but I was able to update the existing record with a tag. Not quite what I wanted, but it will work.