1 · Backend connection
Use the deployed PALCYAI owner/chief command endpoint only after confirming its request schema. Do not use a Supabase service-role key in the browser.
Template placeholders: {{worker_id}}, {{worker_name}}, {{message}}. This default is a generic example, not a claim about your function’s accepted schema. Confirm it against the deployed source before testing.
2 · Live evidence
Not production proof
HTTP 2xx alone does not prove a worker completed its task or that a database, sheet, email, call, or booking changed. Verify the returned execution ID and destination record independently.
No payment is initiated by this page. No real client outreach, calls, bookings, or social posts are triggered intentionally by this console.
3 · Individual worker workspaces
Each worker has a separate message box and response log. Requests are sent only to the endpoint configured above.
4 · Provider login handoffs
Open a handoff, complete sign-in and any verification yourself, then click Save profile on the setup page. Never send passwords or MFA codes in chat.
Sign in at the canonical dashboard.
Open n8n browser handoff ↗Complete login and required verification.
Open Meta browser handoff ↗Uses a separate saved browser profile; Meta may ask for verification again.
Open WhatsApp browser handoff ↗These are browser sign-in handoffs, not proof that the accounts are connected or authorized. After saving, return to the chat and tell me which provider profiles saved successfully.
5 · Acceptance checks before activation
These boxes are a local checklist only; checking them does not alter or activate any remote service.