I’ve been lurking around here for a while - this forum’s been super useful to me in the past, but I’ve hit a snag and could use some help.
I’m trying to send the uploaded image (or URL) from a chatbot to a Zapier webhook.
The chatbot allows users to upload images, and I can see the uploaded file has a URL (something like https://prod-pickaxe-assets.s3.us-west-2.amazonaws.com/...).
What I need to do is capture that URL and include it in a webhook payload that sends data to Zapier.
The webhook works fine for text-based data but I can’t figure out how to properly extract the image URL from the chatbot and include it in the request. I tried prompting it for the URL within the payload description but no joy.
Does anyone know the best way to reference the uploaded file’s URL within Pickaxe?
Is there a way to store the image URL as a variable and pass it into the webhook payload?
Some threads I referenced, it seems like the user uploaded attachments are retrievable but I just can’t figure it out. And I am not capable of creating custom Actions like some of you clever dudes:
Apologies for digging up an old thread but I’m trying to send files over a N8N webhook payload and it doesn’t seem to be possible. I see that this was supposed to be resolved a few months back (although I’m not sure if the abovementioned fix was specific to Zapier or for all webhooks). Any information or update on this would be greatly appreciated as it is fundamental or something I’m working on. Thanks.
You’ve raised a question that’s front-and-center for anyone serious about scaling their Pickaxe Knowledge Base with live external data. Here’s my expert synthesis, combining the latest research, community insight, and direct experience:
1. Capturing the Uploaded File/Image URL:
When a user uploads a file or image in your Pickaxe chatbot, Pickaxe does generate a URL for that upload. This URL is often visible in the chat log, but the real trick is referencing it programmatically.
The variable for this URL is typically something like {{upload.file_url}}, but the actual syntax can vary depending on the configuration or the update cycle of the Pickaxe platform.
In the Builder, check the output variables or the documentation for a list of available placeholders. If you see a variable exposed for the uploaded file URL (sometimes called attachment_url, file_url, or similar), that’s the one you want to use.
2. Defining Your Data Payload with Function Inputs:
Before you can structure your webhook payload, you first need to tell Pickaxe what data to send. You do this using Function Inputs within the Action’s settings. This is a critical step for any automation platform, whether it’s Make, Zapier, or N8N.
For example, you would set up a function input like this to capture the file URL:
As you can see in the example setup above, you would create an input (e.g., named uploaded_file_url). You can then reference this input in your webhook payload. For a webhook action, the JSON payload might then look like this:
Zapier: The Pickaxe-Zapier integration has had recent improvements, and it’s now usually possible to pass the uploaded file URL directly in the webhook payload once you’ve defined it as an input.
N8N: The process is similar, but support for direct file URL embedding may lag behind Zapier. If the variable isn’t available, you might need a workaround: have Pickaxe echo the file URL as part of a chat message, or use an intermediary service to parse the chat data for URLs before sending it on to N8N.
4. If the URL Variable Isn’t Exposed:
Sometimes, Pickaxe doesn’t expose the file URL as a variable in your webhook builder—especially if you’re not using custom Actions. In that case:
Try to create a step in your conversation flow that explicitly outputs the file URL as part of a message or summary, which you can then parse.
If that’s not feasible, consider using a middleware (like a lightweight script or service) to intercept the webhook, extract URLs from the text, and forward them to Zapier/N8N.
5. What to Watch Out For:
Not all webhook destinations treat file URLs the same way. Some might expect public URLs, others need authentication. Always test the entire flow from upload to webhook to downstream platform.
Pickaxe platform updates can alter variable names or expose new ones—revisit the docs every so often.
If you rely on a middleware workaround, factor in error handling for cases where uploads fail or URLs are malformed.
Why this approach? It keeps your integration low-code and leverages standard Pickaxe capabilities, minimizing maintenance overhead. And it means you don’t have to build or maintain custom Actions, which is a big plus for most users.
