OpenClaw connector & integration - any thoughts or plans?

[tonydehnke]

It seems like a private hosted thing like Campfire would be fantastic to use with Openclaw to keep the chats, messages etc private vs the popular options like Telegram, Discord etc.

Is there a reason that there has not been any development of a connector or way to integrate with Openclaw?

[monorkin]

Hey @tonydehnke I haven't yet used OpenClaw so I'm not sure what a connector does. But Campfire does have a Bot API which allows bots to post and receive messages. Would that be sufficient?

[tonydehnke]

Possibly, will see how that could integrate.

[frankdierolf]

I already have a intergration.
openclaw/openclaw#7883

Love it! Customers like it as well.

One issue is that images, videos, every attchment can easily send via the @openclaw tag because it lands in a seperate message. So had to built around it. I created a campfire-context skill which logs in as User and there he can read images, pdf, etc. Its a bit tidious and the current bot setup is not ideal. Also voice message are not avaialbe which is a bit of a downer.

Would love to integrate it, if one of the maintainer is intrested, happy to throw a pr to add functionality to the current campfire source code.

@monorkin @tonydehnke

Liking the pr also is a support to push native integration. If it lands it is possible to built a tiny comunity around it. 😁

[hrgrvs]

I'd also like to see this developed. We need an API so you can just message your Openclaw agent to share files, instructions, etc. I don't think that a webhook is going to be enough.

One of the great benefits of using Campfire is that your communication with your agent can be in closed system that you own, and it doesn't require an email address.

[frankdierolf]

@damonhargraves I have a skill to do it. Its basically a cli + markdown file.
The cli logs into an account and there he can read messages on diffrent groups etc. Works quite nice. I thinking about to make it public, but yeah its is a bit hacky and it would be better to enable read and write to campfire that would get rid of a lot of hassle.
I also tested it with my own fork, it literally just 20 lines of code changes to get it natively in there. But in the past it was read write with a bot but got removed because simplicity first, which I totally subscribe towards. In this case it might needs a rethink.

[poondq]

this will be cool usecase

[jaredatch]

@frankdierolf In lieu of the PR being closed, do you plan to package it up and put on npmjs as a plugin? 🍻

[frankdierolf]

@jaredatch Working currently on it. Join my little campfire playground to interact with it.
https://chat.lay.haus

There is still the problem with reading messages. The problem with rendering the text in html is solved thruh the message tool hints that openclaw now provides. Yeay.
But reading messages is still a hussle :/

Here is the new pr:
openclaw/openclaw#35939

Lets see if it goes in. If not, then either me does a npm package, not a fan of it because to keep up with the pace of development is a bit^^ Or maybe a someone from the the campfire team would love to do one? 👀

Cheers ✌️