Sending a message with Chatbase API

Hi all! Happy to be here!

I can see n8n and ChatBase integration here: Chatbase integrations | Workflow automation with n8n

However, I’m not seeing its node in my self-hosted community edition. Does this mean its included in paid, but not in community version of n8n? If so - any option to still have it in my self-hosted n8n?

Thank you!

Regards,

Dan

Hey @Dan_Burykin,

It looks like for that one you need to configure the HTTP Request node to connect to ChatBase so it isn’t a standard node but rather something that we know will work with n8n with a bit of configuration.

1 Like

Got it. Well, I’m not super tech savvy, so it might take quite some of my time. It’s just prior to this I had dev and she did that sort of integration for me, but I believe she faced issues with delays etc. I would so much appreciate if you could forward me with some template of connecting my ChatBase via HTTP request node and maybe the rest of somethings to efficiently process all these typical issues with in case if there is no ready to use node for such API. Like I can see you have something for OpenAI API, but still I’m a newcomer, so not sure if I could adapt it.

Thank you very much!

Regards,

Dan

1 Like

Hi again @Jon and @n8n_Team . I’m not saying I’m already and expert in your HTTP node, but I managed to connect to SendPulse API via it. Still, I can’t send message (and receive reply) via ChatBase API. It seems much easier than SendPulse API, but still, tried everything. Couldn’t find any hint in all 2 other threads related to ChatBase here. Kindly ask you to advise. Thanks a lot!

Regards,

Dan

P.S. Sorry, not sure if I can share my workflow with the self-hosted community edition plan.

1 Like

Yes you can, Select All in the workflow editor and Paste here by clicking on this button.

Thanks @mcnaveen . Here yes, but I can’t get the code from N8N

Screenshot 2024-07-18 at 12.54.28

1 Like

No, Just Press ⌘+A to select all the nodes in the workflow then ⌘+C to Copy it. Then here in the community you can right click to paste it.

If you’re on windows. It’s Ctrl Key.

Export-1721300394321

Wow. Thanks, @mcnaveen . Here it is. Disregard SendPulse node, just let me know how to authorise and message N8N (THANK YOU!):

Yeah, yeah, I finally found it, @mcnaveen . Thanks. Didn’t work first 2 times lol. So disregard the SendPulse API call via HTTP node. Kindly let me know how to authorise the message to my ChatBase Chatbot via it’s API with also HTTP node. Thanks a lot!

Oh gosh. Yeah, I solved it soon, but. Apparently I’ve been posting and editing too often, so that system is now hiding my posts…(((

ah sad. Not an issue. If you can’t solve it. Feel free to create a new thread in the forum a bit later.

P.S: I don’t have permission/access to move it out of spam.

okay. the posts have finally went through, @mcnaveen

Sorry about that, something in them triggered the forum’s spam filter and I had to approve them.

1 Like

No worries. @bartv @mcnaveen any advice you could give me on the HTTP node that fails to authorise ChatBase? The workflow is posts above and here below:

Okay. First of all. Since there are a lot more replies here, I converted this topic from “Feature Request” to “Question” type.

Feel free to create another topic for Chatbase Node as “Feature Request”.

Answering your question. Here in the Chatbase docs. Message a Chatbot they gave an example.

So instead of mapping it using the fields option. Can you try sending it as JSON?

Why because, the documentation states the message should be array.

An array containing the ALL the messages between the user and the assistant. Each message object should have content and role properties. The content field represents the text content of the message, and the role field can be either “user” or “assistant” to indicate the sender of the message.

1 Like

OMG! It’s worked! Thank you so much, @mcnaveen !

1 Like

Glad it worked. Please mark the answer as Solution.

Thank you :blush:

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.