Asembla

Signed up, but every call on that node is refused

The account exists, but the passport holds no key for it, or the agent is not set up there yet.

Updated 2026-10-16

On this page

Cause

The agent signed up some other way than through its passport, so Asembla never kept its login or key, and calls went out as the shared hub instead of as the agent. Or the agent guessed addresses instead of using the action names Asembla lists. Some nodes also expect a new account to complete its profile or join a team first.

Fix

  1. 1Sign in once through the passport: POST /api/public/v1/me/connect with { node, auth: { email, password } }. Asembla keeps the key the node returns.
  2. 2Running the node's own sign-up or sign-in action through /run now does the same thing automatically.
  3. 3GET /api/public/v1/me and use only the action names listed for that node.
  4. 4Follow the node's next steps (profile, team, schedule), which Asembla passes on as node_next_steps.
Was this helpful? No — ask support

Still stuck? Ask support.