Client setup — WhatsApp or Telegram to LinkedIn draft workflow

Who this is for: You're getting a workflow from us that turns your WhatsApp or Telegram messages (or voice notes) into on-brand LinkedIn post drafts. This guide explains what you need to do so we can build it and you can run it safely. Complete the steps in order; we'll use your accounts so you stay in control of cost and access.

What you get: When you send a message (or voice note), the workflow sends you back an on-brand LinkedIn post draft. You'll see it in the same chat (WhatsApp or Telegram) so you can copy and paste into LinkedIn—or wherever you publish. If we've agreed a draft store (e.g. a shared folder or Notion), we'll also save each draft there so you have one place to find and edit drafts before publishing. We'll confirm where your drafts go when we agree scope.

What we do vs what you do

We: Design and build the workflow, configure it in your tools, and give you a short checklist and one handover call when it's ready.

You: Create the accounts below, invite us so we can manage and configure your n8n, model provider, and messaging channel (WhatsApp or Telegram). You set usage and budget limits so you control spending. You own the accounts; we get access only to build and configure, and you can remove us after handover.

Want us to handle as much as possible? You only need to do the bits only you can do: create each account and invite us (or share the Telegram bot token). We'll do the rest—webhooks, credentials in n8n, workflow build, and testing. The steps below are the same; we're just making clear that once you've invited us, we take over. If you prefer, we can do a short setup call and do it together: you create and invite, we guide you and then configure everything. Ask us when we send you this guide.

Sharing credentials safely

In the steps below you may need to share credentials with us: API keys (Claude, OpenAI), WhatsApp access token, or Telegram bot token. We only put these into your n8n; we don't store them in our systems. How to share them safely:

Best fallback (recipient doesn't need an account):

Bitwarden Send — Recommended when you need to share a credential with someone who doesn't use your password manager. Bitwarden Send lets you create a secure link to a secret; the recipient (us) can open it in a browser and copy the credential once—no Bitwarden account required. You send us the link (e.g. by email or message). Set a short expiration (e.g. 1 hour or 1 day) and "maximum access" to 1 if available. Best option if you don't have a shared password manager or secure-send feature.
Other one-time link tools — If we send you a one-time secure link from another tool, paste the credential there; we read it once and the link expires.

If you use a password manager:

1Password, Bitwarden, etc. — Use your app's "share" or "secure send" to our email (we'll give you the address). We open the link, copy the credential into your n8n, and don't retain it.

If you prefer not to use a link:

Voice call — On a short call, read the key or token out once; we type it into your n8n. After the call, delete any local copy (e.g. from Notes) and you can rotate the key/token later if you want.

Don't: Send credentials in normal email, group chat, Slack channel, or SMS. Don't paste them in a shared doc or ticket others can see. That way they're not stored in plain text or visible to others.

After handover: You can revoke or rotate any key or token (Claude/OpenAI in their console, WhatsApp/Telegram in Meta / @BotFather) and update the new value in n8n; we won't have access after that.

Step 1: n8n (where the workflow will run)

What to do:

Create an n8n Cloud account at n8n.cloud (or we can use ours and migrate to you later—we'll tell you).
Once you're in, go to Settings (three dots next to your profile, bottom left) → Users.
Click Invite and enter the email address we give you. We'll accept the invite and then build the workflow in your workspace.

Why: So we can build in your space and you own it from day one. No export/import at handover. Adding us doesn't add a per-seat cost (n8n Cloud plans include unlimited users). For pricing (e.g. Starter ~€20/mo, Pro ~€50/mo), see n8n Cloud pricing.

Step 2: Model provider (OpenAI or Anthropic)

We'll tell you which one we're using (OpenAI or Anthropic/Claude). Choose one of the options below.

Option A: Invite us to your organization

What to do:

Create an organization (not just a personal account):
- OpenAI: platform.openai.com → create or use an organization.
- Anthropic: You need an organization (e.g. Team or API org); individual accounts can't invite. See Anthropic: managing members.
Invite us:
- OpenAI: Organization Settings → Members → Invite → enter our email. OpenAI: add members.
- Anthropic: Admin settings → Organization → Add member → our email (invites expire after 21 days).
Set a monthly budget limit and an alert:
- OpenAI: In the platform go to Settings → Billing / Limits (account/limits). Set a monthly budget and turn on email (or SMS) alerts at e.g. 80% so you're warned before hitting the cap.
- Anthropic: In the Claude Console open the Limits page; set or confirm user-configurable limits for your workspace so spend is capped as you want.

Why: You pay for model use and control spend. We get access to configure the workflow without holding your billing or keys. Limits prevent runaway cost.

Option B: Claude API key (for Pro or individual users)

If you're on Claude Pro or don't have an Anthropic organization, you can create an API key and share it with us. We'll add it only to your n8n workflow and won't store it elsewhere. Your Claude Pro subscription on claude.ai is separate from the API; the workflow uses the API, so you add a small amount of credits (e.g. $5) and can set a monthly limit to keep costs low.

What to do:

Open the Claude Developer site: In your browser, go to platform.claude.com/settings/keys.
Sign in or create an account: Sign in with your email (or the same one you use for Claude), or sign up and choose Individual when asked.
Create an API key: Click Create key (or Create API Key). Give it a name (e.g. "n8n workflow" or "LinkedIn draft workflow"). If it asks for a workspace, leave the default. Click Create.
Copy the key immediately: The key is shown only once. Click Copy (or select it and copy). Paste it somewhere safe temporarily so you can send it to us in the next step.
Add credits: The API needs credits to work. In the left menu click Billing (platform.claude.com/settings/billing) and add at least $5 in credits. You can add more later.
(Optional) Set a spend limit: In the left menu click Limits (platform.claude.com/settings/limits). If you see a monthly spend limit, set it (e.g. $10 or $20) so usage is capped.
Send the key to us securely: Use one of the methods in Sharing credentials safely (e.g. Bitwarden Send, or a quick call). We'll put it only into your n8n workflow.

Why: You keep control of billing and the key. We configure the workflow without holding your key in our systems. You can delete or rotate the key in platform.claude.com/settings/keys after handover if you like.

Step 3: Messaging channel (WhatsApp or Telegram)

Choose one channel. You're inviting us to manage and configure it so we can connect the workflow—we'll set up the webhook and credentials in n8n. After handover you can remove our access (see FAQ below).

Where the webhook URL comes from: The workflow runs in your n8n (Step 1). We build the workflow there and add a Webhook node; that node exposes the HTTPS URL that WhatsApp or Telegram will call. So you must complete Step 1 (invite us to n8n) first. Once we've built the workflow: in n8n, open the workflow → click the Webhook node → at the top of the node you'll see Production URL (and Test URL). Use the Production URL as the Callback URL in Meta (or for Telegram). Activate the workflow (toggle Active on) so the URL is live. We'll send you the URL and verify token, or you can copy them from the workflow. WhatsApp: Meta sends GET to your URL to verify it, then POST for messages. The workflow is set up so the same URL accepts both; if Meta says the URL could not be verified, we'll check that the Webhook node accepts both GET and POST (see runbook).

Option A: WhatsApp (Meta)

We connect via the WhatsApp Cloud API, which is set up in Meta for Developers, not in the WhatsApp Business app on your phone. If you only use the WhatsApp Business app today (the green app with your business profile), you'll create (or use) an app in Meta for Developers, add the WhatsApp product, and link your existing business number in API Setup below. If you already have an app with WhatsApp configured, you may have the credentials already; we'll agree how to use the single webhook.

What to do:

Go to Meta for Developers and sign in.
Create an app (or use an existing one) → Add Product → WhatsApp.
In WhatsApp → API Setup (or Getting Started), add or select your business phone number so it's linked to this app. That's how we get the Phone number ID (we need this to send replies) and WhatsApp Business Account ID (if shown). If your number doesn't appear, ensure the WhatsApp Business Account that owns that number is linked to the same Meta Business Account that owns this app.
Create or copy a permanent access token (for production we use a System User token with whatsapp_business_messaging and whatsapp_business_management). For testing, the temporary token from the setup page is enough. Store it securely.
Invite us to manage your WhatsApp: Share the token with us using one of the methods in Sharing credentials safely (we'll add it to n8n with your permission), or add it yourself in n8n when we ask. Webhook setup: The webhook URL comes from your n8n workflow (the Webhook node we add when we build it). After Step 1 is done and we've built the workflow, we'll give you that Callback URL and a verify token. You (or we, with your permission) enter them in Meta: WhatsApp → Configuration → Webhook — set Callback URL to the n8n webhook URL and Verify token to the token we give you. Meta will verify the URL; then incoming messages are sent to your n8n workflow. You stay the app owner.

Why: So your WhatsApp number can receive messages and the workflow can reply with the draft. Meta requires HTTPS and a verified webhook.

Using your existing WhatsApp Business account: The steps above are the same whether you're creating a new app or already have one. If you already use WhatsApp Business (e.g. you have a business number and maybe a Meta for Developers app):

Use your existing number and app. You don't need a second number or a second business account. In Meta for Developers, open your app (or create one if you only use the Business app elsewhere) → Add Product → WhatsApp if it's not there → WhatsApp → API Setup. Note Phone number ID and WhatsApp Business Account ID, and create or copy a permanent access token (System User token with whatsapp_business_messaging and whatsapp_business_management for production).
Link your number in this app: In WhatsApp → API Setup, add or select your existing business number so this app has access to it. If the number isn't listed, check that your WhatsApp Business Account is linked to the same Meta Business Account as this app.
One webhook per app: Meta allows only one webhook URL per app. If you already have a webhook (e.g. for another tool or bot), tell us before we connect. We'll agree how to proceed: either you point the webhook to our workflow URL (you may need to pause or move the other integration), or we provide a single URL that receives events and we route to the draft workflow if we support that. Don't change your live webhook until we've agreed.
Share the token with us using one of the methods in Sharing credentials safely. We'll add it to your n8n and configure the webhook with you.

References: Meta: Set up webhooks.

Option B: Telegram

What to do:

In Telegram, open a chat with @BotFather and send /newbot. Follow the prompts to name your bot and get a bot token.
Store the token securely. Invite us to manage your Telegram bot: Share the token with us using one of the methods in Sharing credentials safely. Webhook setup: The webhook URL is the same n8n Webhook node URL from your workflow (Step 1 must be done first so we can build it). We'll register that URL with Telegram using your token via the Telegram Bot API, so messages to your bot are sent to your n8n workflow. We'll do this after we've built the workflow; you don't need to enter the URL anywhere yourself unless we agree otherwise. You remain the bot owner and can revoke or rotate the token after handover if you want.
No phone number or Meta app required—Telegram bots are free.

Why: So messages (or voice notes) sent to your bot are received by the workflow and the draft is sent back. Simpler setup than WhatsApp if you're happy using a Telegram bot as the entry point.

Step 4: Brand content

What to do:

Share your voice and tone (how you want to sound), key messages (2–5 points you want to reinforce), and content pillars or themes (optional). We can do this in a short call and we'll turn it into the format the workflow needs, or you can send bullets or a doc.

Why: So the LinkedIn drafts sound like you and stay on message. The workflow uses this to generate on-brand copy.

Step 5: After we build

What happens:

We'll send you a short credential and setup checklist (what's connected, where to set or update limits, how to trigger the workflow, and where your drafts are delivered—in the chat and, if agreed, in your draft store).
We'll schedule one handover call to walk through the workflow, confirm it runs, and show you where to change limits or content if needed.
After that, you run it yourself. If you need ongoing support, we can agree a maintenance option.

Why: So you can run and own the workflow after we step back, and you know where to find your drafts and where to look if something changes.

FAQ

Can I reduce my paid plan or remove your access after the workflow is set up?

Yes. After handover we no longer need access. You can:

n8n: Remove us from Settings → Users (we'll no longer be a member).
Model provider (OpenAI or Anthropic): Remove our member invite from your organization, or (if you used Option B) delete or rotate your API key in platform.claude.com/settings/keys.
WhatsApp: Revoke or rotate the access token in Meta so the existing workflow keeps working with a new token you store in n8n; we no longer have access.
Telegram: Revoke the bot token in @BotFather and generate a new one, then update the token in n8n; we no longer have access.

Cost: You can often reduce costs once we're off the accounts. For example, you can downgrade your n8n plan (e.g. Pro → Starter) if you no longer need the higher tier; model provider billing is usage-based so you only pay for what you use; Telegram bots are free; WhatsApp/Meta pricing is per conversation. So after handover you're not paying for our access—just your own usage.

I see "Only instance admins can change this" when viewing MCP in Cursor.

Only Cursor instance admins can change Instance-level MCP settings. If you use Cursor with a project we've shared and need MCP (e.g. to connect to your n8n), use project-level MCP: open the project's .mcp.json in the repo (we may have added an n8n MCP entry for your instance). That config applies when you work in this project and doesn't require instance admin rights. If the project doesn't have a .mcp.json with the right server, ask your Cursor instance admin to add the n8n MCP at instance level, or we can add the entry to the project's .mcp.json and share it with you.

Need help?

If anything is unclear or you're stuck on a step, contact us (we'll give you the contact details). We're happy to clarify or do a short call to unblock you.