Skip to content

Kraken

Connect your company’s Kraken account and its activity posts into a channel: a customer’s USDC landing, bitcoin sold for dollars, a withdrawal to your bank, a balance running low. Your finance team sees it within a minute, without logging in to Kraken.

Each card shows the amount, what it’s worth in US dollars, and the details: the network and transaction for a deposit, the price, fee and number of fills for a trade, the fee and new balance for a withdrawal. The cards come from Kraken, so nobody’s account is borrowed.

Only owners and admins can connect Kraken, in Workspace settings → Integrations & apps → Integrations → Finance → Kraken.

Kraken doesn’t send webhooks, so Freesbe asks it. Every minute it reads the account’s ledger, the list of everything that moved, and posts what’s new. When the account has been quiet for an hour, Freesbe checks every five minutes instead, and goes back to every minute as soon as anything happens. A deposit Kraken shows as on its way counts too, so the moment it’s credited posts promptly.

Nothing from before you connected posts, and each thing posts once.

Freesbe only reads your account, so give it a key that can’t move money.

  1. Sign in to Kraken and open Settings → API, then Create API key.
  2. Name it Freesbe and tick only Query Funds and Query Ledger Entries.
  3. Leave everything else unticked: anything that trades, deposits, withdraws or transfers. Freesbe never needs it.
  4. Click Generate key and keep the page open: Kraken shows the private key only once.

Kraken can’t tell Freesbe what a key is allowed to do, which is why it’s worth checking the boxes yourself. Use a separate key for each channel you connect.

  1. In Freesbe, open Workspace settings → Integrations & apps → Integrations → Finance and click Connect Kraken.
  2. Paste the API key and the Private key.
  3. Pick the channel and what to post (below), and click Connect Kraken.

Freesbe checks the key can read your balances and ledger before saving it, and keeps the private key encrypted. Settings show only the key’s last four characters.

When you connect, or later from the account’s ⋯ menu → Edit, pick:

  • Post to channel. Money is private, so a private channel for your finance team works best. Alerts in a private channel are only visible to admins who are in it.
  • Alerts to post:
    • Deposits: Deposit on the way as soon as Kraken sees it, with the network and the transaction, then Deposit received when it’s credited, with the new balance.
    • Withdrawals: Withdrawal sent, with the fee and the new balance.
    • Trades: Bought, Sold or Swapped, with the average price and the fee. Fills of the same order that land in the same minute are added up into one card.
    • Staking rewards and other activity: staking and Earn rewards, transfers between your Kraken wallets, and adjustments. Off at first, since staking rewards arrive often.
  • Smallest amount to post, in US dollars. Activity worth less is left out. Freesbe values each asset with Kraken’s own dollar price; an asset with no dollar market always posts.
  • Balance alerts. Up to ten, like BTC drops below 0.5 or USD goes above 100,000. Each posts once when the balance crosses the line, and again only after it has come back and crossed again. Bitcoin held in Earn counts towards your BTC balance.
  • Daily balance summary. Every holding with its dollar value and the total, once a day at the hour you pick, in your time zone.

From the account’s ⋯ menu:

  • Send a test alert posts a sample card, marked as a sample, into the channel.
  • Turn off stops checking. When you turn it back on, Freesbe carries on from then, without posting what happened while it was off.
  • Disconnect stops checking and deletes the key from Freesbe. Then delete the key in Kraken under Settings → API too.

If Kraken refuses the key, the account shows Can’t read the account and says why, and Freesbe tries again every 15 minutes. That happens when the key was deleted in Kraken or lost a permission. Make a new key as above and click Replace the key. If Kraken is busy or down, Freesbe simply tries again shortly; nothing is lost, because the next check reads everything since the last one.