This guide is for dashboard users. It explains how to create actions and hand the setup to your developer or AI assistant. For the request format, signing and code samples, see Campaign Actions (Developer Guide).
A campaign action is something a prospect can do outside LinkedIn: book a call, open the lead list you sent, visit your pricing page. Your own systems tell Kakiyo when it happens, and Kakiyo’s AI sees it the next time it writes to that prospect.Kakiyo does not track anything itself. Your website, booking tool or backend already knows when a prospect does something, and it reports it to Kakiyo with one signed HTTP request.
How it works
1
Create an action
In a campaign, open the Actions tab and click New action. Give it a name and write what it means for the AI.
2
Connect your system
Each action has its own webhook URL and signing secret. Your server sends a signed
POST to that URL with the prospect’s LinkedIn URL (or Kakiyo chat id) whenever the action happens.3
The AI uses it
On the next first message, reply or follow-up for that prospect, the AI sees the completed action in the prospect’s custom context, for example: “Booked a call: done on 2026-11-12. Meaning: Don’t pitch again; confirm the time.”
Example uses
Creating an action
- Open Campaigns, click a campaign, and choose the Actions tab.
- Click New action.
- Fill in:
- Name: short and clear, e.g. “Booked a call” (max 60 characters).
- What it means for the AI: one or two sentences telling the AI how to react, e.g. “The prospect booked a discovery call. Do not pitch again; confirm the time.” (max 500 characters).
- Signing secret: let Kakiyo generate a secure secret (recommended), or use your own secret (24 to 128 characters, no spaces).
- Click Create action. The full secret is shown right away. Copy it and give it to whoever sets up the integration. They should store it on their server as
KAKIYO_ACTION_SECRET.
Setting it up without writing code yourself
Every action has a Setup guide button. It opens a panel with:- the webhook URL and how to sign the request;
- the exact request body and every possible response;
- ready-to-use cURL, Node.js and Python examples;
- a Copy AI setup prompt button. Paste the prompt into ChatGPT, Claude or Cursor and it writes the integration for your stack. The prompt never contains your secret: the code reads it from
KAKIYO_ACTION_SECRET.
Seeing completed actions
Open a conversation in the Inbox and click the prospect’s name, or open a prospect from Prospects. Under Custom Data, Completed actions lists every action the prospect completed, how many times, when, and the details your system sent. You can remove a completed action that was sent by mistake with the × next to it. The AI stops seeing it right away.Managing actions
On each action card you can:- Copy the webhook URL.
- Reveal or copy the signing secret.
- Rotate the secret: generate a new one or set your own. The old secret stops working immediately, so update your server right after.
- Edit the name and meaning.
- Delete the action. Its URL stops working and it is removed from every prospect in the campaign.
Any team member can create actions and edit their name and meaning. Revealing, rotating or deleting a secret is limited to team owners and admins, and to the person who created the action.
FAQ
Does Kakiyo track website visits or bookings itself?
Does Kakiyo track website visits or bookings itself?
No. Your systems decide when an action happened and send it to Kakiyo. Kakiyo only receives it and passes it to the AI.
Does it overwrite the custom data I wrote for a prospect?
Does it overwrite the custom data I wrote for a prospect?
No. Completed actions are added after your custom data when the AI writes, and your custom data is never changed.
What happens if the same event is sent twice?
What happens if the same event is sent twice?
If your system sends an
eventId, retries of the same event are not counted twice. Without it, every request counts as a new completion and increases the count.Can I call the URL from a web page in the browser?
Can I call the URL from a web page in the browser?
No. The request must be signed with your secret, and a secret in a web page is public. Always send it from your server, a serverless function or an automation tool’s code step.