# N8N and Fibery Integration Error (RichText)

**URL:** <https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959>\
**Category:** Get Help\
**Created:** [June 10, 2025, 7:59pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959 "2025-06-10T19:59:44Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 10, 2025, 7:59pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/1 "2025-06-10T19:59:44Z")

</div>

Hello everyone. I really need your help. I’ve been trying to solve this issue for two days already.

I’m trying to send data from Telegram to Fibery into a specific database. I’m creating a very simple workflow in N8N.

Workflow:

1. A message is sent to a Telegram bot.
2. The first line of the message is used for the Name field to create an entity in the “Content” database of the “Idea” space.  
The rest of the message content should be added to the Description (RichText) field.

The first and second steps work. However, I can’t manage to send the text to the Description (RichText) field.

No AI model has been able to help with this, even when I provided almost all the Fibery API details. I keep getting errors.

It seems like I need to create two additional steps to retrieve the secret for the Description field and then update it. I tried setting up two sequential HTTP Requests in N8N, but it hasn’t worked so far.

Maybe someone has a ready-made solution for this task? Or could you suggest what I need to study to implement this?

I suspect I might have missed something in the setup process.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3c224be23853cce3cce98df34f380981541c8919.png)

---

<div class="post-metadata">

**Author:** ![Viktar\_Zhuk](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/viktar_zhuk/32/1934_2.png) [@Viktar\_Zhuk](https://community.fibery.io/u/Viktar_Zhuk)\
**Post date:** [June 11, 2025, 8:37am UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/2 "2025-06-11T08:37:01Z")

</div>

Sorry for jumping in, I have no knowledge about N8N. But as far as you’re using http request you can try graphql mutation. It can create an Entity and set (append) Description in one call.

look at this example [Fibery](https://the.fibery.io/@public/User_Guide/Guide/GraphQL-mutations-256/anchor=Mutations--e546c83f-a803-43fb-af52-64b4bd08e0bd)

Hope this helps

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 9:06am UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/3 "2025-06-11T09:06:31Z")

</div>

Now I’m in the following situation.  
Here’s the general workflow:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/14aa8cb8a8880a694aef93ab50b9854eae150cd8.png)

Here’s the JSON in the block for the “secret” request.

```auto
{{ JSON.stringify([{
  command: "fibery.entity/query",
  args: {
    query: {
      from: "My Space/My DB",
      select: [
        "fibery/id",
        {
          path: ["My Space/Description", "Collaboration~Documents/secret"]
        }
      ],
      where: {
        "My Space/Name": {
          eq: $json.result["My Space/Name"]
        }
      },
      limit: 1
    }
  }
}]) }}

```

But I keep getting the following response.

```auto
[
  {
    "success": false,
    "result": {
      "name": "entity.error/schema-type-not-found",
      "message": "null database was not found.",
      "data": {
        "top": {
          "error/name": "entity.error/schema-type-not-found",
          "error/schema-version": 8080,
          "type": null,
          "query": {
            "from": "My Space/My DB",
            "select": [
              "fibery/id",
              {
                "path": [
                  "My Space/Description",
                  "Collaboration~Documents/secret"
                ]
              }
            ],
            "where": {
              "My Space/Name": {
                "eq": "test"
              }
            },
            "limit": 1
          }
        },
        "cause": {
          "error/name": "entity.error/schema-type-not-found",
          "error/schema-version": 8080,
          "type": null,
          "query": {
            "from": "My Space/My DB",
            "select": [
              "fibery/id",
              {
                "path": [
                  "My Space/Description",
                  "Collaboration~Documents/secret"
                ]
              }
            ],
            "where": {
              "My Space/Name": {
                "eq": "test"
              }
            },
            "limit": 1
          }
        },
        "error/schema-version": 8080,
        "type": null,
        "query": {
          "from": "My Space/My DB",
          "select": [
            "fibery/id",
            {
              "path": [
                "My Space/Description",
                "Collaboration~Documents/secret"
              ]
            }
          ],
          "where": {
            "My Space/Name": {
              "eq": "test"
            }
          },
          "limit": 1
        }
      }
    }
  }
]

```

The database and space names have been verified, and everything matches in the schema. I can’t figure out why the request isn’t going through.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 11, 2025, 9:20am UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/4 "2025-06-11T09:20:21Z")

</div>

I haven’t used N8N, but wouldn’t you structure the body of the http POST request according to the [user guide](https://the.fibery.io/@public/User_Guide/Guide/Entity-API-264/anchor=Select-rich-text-Field--f9838a54-3d74-4f49-9f5d-9195731c7e89).

e.g.

```auto
[
   {
     "command": "fibery.entity/query",
     "args": {
       "query": {
         "q/from": "My Space/My DB",
         "q/select": [
           "fibery/id",
           { "My Space/Description": ["Collaboration~Documents/secret"] }
         ],
         "q/limit": 1
       }
     }
   }
]

```

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 10:17am UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/5 "2025-06-11T10:17:29Z")

</div>

Thanks.  
It looks like it worked. I’m just far from programming and simply provided the instruction to the neural network. But they didn’t give me such a response))).  
Now it remains to complete the step of updating the Description.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/712253035c5536a9b11565a7a9a857ba60045328.png)

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 10:51am UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/7 "2025-06-11T10:51:33Z")

</div>

In the last module, the JSON is as follows:

```auto
{{ JSON.stringify({
  command: "Collaboration~Document/patch",
  args: {
    secret: $json.result0"My Space/Description""Collaboration~Documents/secret",
    patch: {
      type: "md",
      content: $('Edit Fields').item.json.description"fibery/rich-text"0.text
    }
  }
}) }}

```

This causes an error.

```auto
{
  "errorMessage": "JSON parameter needs to be valid JSON",
  "errorDetails": {},
  "n8nDetails": {
    "nodeName": "HTTP Request2",
    "nodeType": "n8n-nodes-base.httpRequest",
    "nodeVersion": 4.2,
    "itemIndex": 0,
    "time": "6/11/2025, 1:44:04 PM",
    "n8nVersion": "1.95.3 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "NodeOperationError: JSON parameter needs to be valid JSON",
      " at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts:355:15)",
      " at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1185:9)",
      " at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1534:27",
      " at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2098:11"
    ]
  }
}

```

Perhaps this is also mentioned somewhere in the documentation. But everything I found doesn’t work.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9e15240b16d2571ce6f2a90b233727a5e69d9d4c.png)

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 11, 2025, 12:02pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/8 "2025-06-11T12:02:56Z")

</div>

If you’re trying to update a document/rich text field, then you can use the method shown in [the guide](https://the.fibery.io/@public/User_Guide/Guide/Entity-API-264/anchor=Update-rich-text-Field--d4691f02-6dcc-4bae-b0c8-c627d90011e8), e.g. something similar to this:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0d34db2e28edae9dfc2e42f6c408d19535b698eb.png)

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 12:28pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/10 "2025-06-11T12:28:30Z")

</div>

Yes, I tried doing that. But the examples provided there don’t work after being formatted into clean JSON. There likely needs to be some specific request structure for Fibery to accept it and update the Description field.

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 12:36pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/11 "2025-06-11T12:36:28Z")

</div>

We urgently need integration with N8N without these complications. If it’s not frequently requested, that’s because no one knows about the possibilities that could be available. The lack of established demand doesn’t mean there’s no market opportunity.

Even if it’s not a full-fledged integration, at least a description of basic use cases: creating entities, retrieving data from entities, and so on. This could be done in a single article in 1-2 hours by someone familiar with Fibery’s API and APIs in general. The value of such a solution would be hard to overestimate.

This is just a wish ))).

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 11, 2025, 12:42pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/12 "2025-06-11T12:42:49Z")

</div>

> [@aklavrov](#):
>
> I tried doing that. But the examples provided there don’t work after being formatted into clean JSON. There likely needs to be some specific request structure for Fibery to accept it and update the Description field.

What does your POST request look like?

> [@aklavrov](#):
>
> We urgently need integration with N8N without these complications. If it’s not frequently requested, that’s because no one knows about the possibilities that could be available.

We will probably get round to it at some point, but there are currently other priorities.  
Out of curiosity, what advantages do you see that N8N has over say Zapier or [make.com](http://make.com) ?

> [@aklavrov](#):
>
> Even if it’s not a full-fledged integration, at least a description of basic use cases: creating entities, retrieving data from entities, and so on. This could be done in a single article in 1-2 hours by someone familiar with Fibery’s API and APIs in general.

I don’t mean to sound churlish, but if you’re using N8N to sent http POST requests, then there is not much specific to Fibery+N8N to be explained. POST is just a standard mechanism, so it shouldn’t matter if you’re using N8N to send a POST request or using any other REST API client.

Of course, there are plenty of people who think that the [Fibery API is hard to understand](https://community.fibery.io/t/more-programmer-friendly-api-docs/8030), but I don’t think that’s an issue exclusive to N8N.

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 1:10pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/13 "2025-06-11T13:10:32Z")

</div>

> [@Chr1sG](#):
>
> We will probably get round to it at some point, but there are currently other priorities.

👌🏻

> [@Chr1sG](#):
>
> Out of curiosity, what advantages do you see that N8N has over say Zapier or [make.com](http://make.com) ?

The ability to host locally or on your own server. Control over data.

> [@Chr1sG](#):
>
> I don’t mean to sound churlish, but if you’re using N8N to sent http POST requests, then there is not much specific to Fibery+N8N to be explained. POST is just a standard mechanism, so it shouldn’t matter if you’re using N8N to send a POST request or using any other REST API client.
> 
> Of course, there are plenty of people who think that the [Fibery API is hard to understand](https://community.fibery.io/t/more-programmer-friendly-api-docs/8030), but I don’t think that’s an issue exclusive to N8N.

Sure, the issue isn’t that, but rather that I’m not a programmer. The advantage is that even a non-programmer can connect a lot in N8N without knowing anything about standard POST requests. But not with Fibery 😁. Fibery has tons of features I’d love to use with N8N. That’s why I’m spending my time on this.

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 1:27pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/14 "2025-06-11T13:27:11Z")

</div>

> [@Chr1sG](#):
>
> What does your POST request look like?

Now I’m in the following situation.  
Here’s the general workflow:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/65926e52df100292c65cc997fa0964621aab4536.png)

Here’s how the module looks inside.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d919c1cfcc593ecaaec55081e9446ccf01963aa1.png)

URL:

`https://workspace.fibery.io/api/documents/{{ $json.result[0]['My Space/Description']['Collaboration~Documents/secret'] }}?format=md`

When  
`{{ $json.result[0]['My Space/Description']['Collaboration~Documents/secret'] }}`  
is secret (Description)

JSON. Body

```auto
{
  "content": "{{ $('HTTP Request').item.json.result['My Space/Name'] }}"
}

```

If I make a request like in this video, then

```auto
[
  true
]

```

And the Description doesn’t get updated.

I tried adding text that should go into the Description, consisting of multiple paragraphs. But then an error is returned.

JSON. Body

```auto
{
  "content": "{{ $('Edit Fields').item.json.description['fibery/rich-text'][0].text }}"
}

```

Error

```auto
  "errorMessage": "JSON parameter needs to be valid JSON",

```

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 11, 2025, 1:49pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/15 "2025-06-11T13:49:38Z")

</div>

> [@aklavrov](#):
>
> And the Description doesn’t get updated.

Have you tried updating the Description with static text, rather than a dynamic value, just to check that the API call is working OK?  
I wonder if `{{ $('HTTP Request').item.json.result['My Space/Name'] }}` is empty or not valid markdown.

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 2:02pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/16 "2025-06-11T14:02:32Z")

</div>

Yes, I tried this:

```auto
{
  "content": "Message"
}

```

and didn’t see the Description updated in any of the entities.

It might be necessary to add some identifier to this JSON, like fibery/id or something similar. Perhaps Fibery doesn’t understand what needs to be updated.

P.S. It was the third day 😄

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 2:04pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/17 "2025-06-11T14:04:42Z")

</div>

Oh, I found the word “Message” in the Description field of one of my entities.

So the JSON itself works. But it updates a random entity.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 11, 2025, 2:26pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/18 "2025-06-11T14:26:45Z")

</div>

> [@aklavrov](#):
>
> It might be necessary to add some identifier to this JSON, like fibery/id or something similar. Perhaps Fibery doesn’t understand what needs to be updated.

> [@aklavrov](#):
>
> So the JSON itself works. But it updates a random entity.

It is updating whatever rich text field has the secret that you pass in the URL for the PUT request:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0200dc56698925c2133a6b8fc0ac985b3f0c12f9.png)

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 2:32pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/19 "2025-06-11T14:32:28Z")

</div>

With the help of Fibery’s support bot, I figured out that in the previous step, the HTTP Request Query needed a JSON change. Also, earlier, I had to set a variable to store the fibery/id.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a7883706e0c9fed3fb3c467479c6dca1ce275ee9.png)

SET

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1bf2a63716956de340a8b0138953cd4108706c64.png)

HTTP Request Query

```auto
[
  {
    "command": "fibery.entity/query",
    "args": {
      "query": {
        "q/from": "My Space/Content Ideas",
        "q/select": [
          "fibery/id",
          {
            "My Space/Description": [
              "Collaboration~Documents/secret"
            ]
          }
        ],
        "q/where": ["=", ["fibery/id"], "$id"],
        "q/limit": 1
      },
      "params": {
        "$id": "{{ $json.entityId }}"
      }
    }
  }
]

```

And it worked))). “Message” was added to the correct Description.

Now, I just need to check how to send text with multiple paragraphs))).

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 11, 2025, 3:08pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/20 "2025-06-11T15:08:08Z")

</div>

> [@aklavrov](#):
>
> Now, I just need to check how to send text with multiple paragraphs

If you haven’t already seen it, you will probably want to read [this](https://the.fibery.io/@public/User_Guide/Guide/Markdown-Templates-53)

---

<div class="post-metadata">

**Author:** ![aklavrov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/aklavrov/32/6715_2.png) [@aklavrov](https://community.fibery.io/u/aklavrov)\
**Post date:** [June 11, 2025, 3:18pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/21 "2025-06-11T15:18:51Z")

</div>

The issue turned out to be with N8N’s internal interpretations, as I understand it.  
With the help of Fibery’s support bot, we got to the bottom of the issue and, after a few iterations, reworked some modules.

Now it works.

I’ll share some key points shortly.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 11, 2025, 3:23pm UTC](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959/22 "2025-06-11T15:23:18Z")

</div>

> [@aklavrov](#):
>
> Now it works.

🥳

[Next page](https://community.fibery.io/t/n8n-and-fibery-integration-error-richtext/8959.md?page=2)