Dynamic Site Awareness for Pickaxe Chatbot Embed Code

Feature Requests
1

Feature Request: Dynamic Site Awareness for Pickaxe Chatbot Embed Code

Overview
I would like to request a feature enhancement for the Pickaxe javascript embed to enable it to dynamically recognize the website on which it is embedded. The goal is to use the same Pickaxe across multiple domains while allowing the embed code to pass a variable (e.g., site_url) to the chatbot.

Use Case
This feature would allow the chatbot to provide contextually relevant links and information based on the specific website it is embedded on. For example, when a client interacts with the chatbot for assistance, it could provide direct, clickable links to key actions on their website, such as the URL for creating a new post. The URLs would automatically adapt to the domain where the chatbot is deployed.

Desired Functionality

  1. Add support for a dynamic variable (e.g., site_url) in the JavaScript embed code to pass the website’s domain to the Pickaxe instance.
  2. Enable the chatbot to utilize this variable to generate context-aware responses with URLs that are specific to the site it is on.
  3. Ensure seamless deployment so the same Pickaxe can be used across multiple domains without the need to create separate instances for each.

Example Scenario

Benefits

  • Simplifies chatbot management by allowing a single Pickaxe instance to serve multiple domains.
  • Enhances user experience by providing relevant, actionable links that adapt to the specific site.
  • Reduces overhead and setup time by eliminating the need for separate chatbot configurations for each domain.

I hope this feature request aligns with your roadmap. Let me know if any additional details or clarification is needed.

2

It cant do that? Have you tested the same bot on multiple sites, my guess would be it should provide context aware content for each embed, as long as you list the domains in the white list section of the pickaxe. I feel like this would be more of a prompt engineering thing than a feature request. Test it out, this seems like something that should work straight out of the box.

3

I’m not 100% sure the Pickaxe will recognize which site it is embedded on. That would be a question for @nathaniel

I think you can either

  1. inform the Pickaxe via natural language in the core prompt by describing which URLs it will be embedded on and how it should act.

  2. Or, for more complex applications, you can use an external action connecting a basic Make.com or Zapier webhook that can branch off into HTTP requests within the workflow, for example.

4

I’ve got a call scheduled with him (and one other) at Noon today 1/2/25

2 Likes
5

I would have thought too. I created one pickaxe that I planned on sharing between multiple websites, the goal is to load the wordpress plugin that I’m working on and then be able to pass it the site URL I want it to think its on. That way I don’t have to go edit the pickaxe each time I load it on a new site. I’d prefer it to be able to just load it dynamically through a variable. I loaded the pickaxe on the website and then straight out asked it what site we were talking on and it said it had no idea.

6

Now that I think about it, it wouldn’t be site aware as the pickaxe is just a tool that communicates with the AI model based on the user input, most AI are not connected the internet by default. Clever prompting would no solve the issue, you might need to play around with a custom action.

7

I’ve had talks with a couple of people today. One voiced interest in what I was doing and shared my screen when talking to them today so that I could show off what I was trying to accomplish. From the sound of it they may be able to put it in the pipeline for what I’m trying to do. Also got invited to a program they’re starting. We’ll see what comes of it.

1 Like
8

The best workaround is to create multiple copies of the tool, each with a different site added in. It’s not elegant, but it’s a start. This functionality is cool, and I’d like to circle back on it after our big late January updates.

9

That’s what I’m waiting patiently for. I think that making this possible could open up the doors to a MAJOR sector when using it with my use case. Not just my clients but 43% of the web.