cTrader Trade Sync connects one or more cTrader identities to Journalit, retrieves broker history, and writes the resulting trades into your Obsidian vault. You authorise each connection through cTrader. Journalit requests read-only account access and cannot place, modify, or close orders.
Read-only means read-only
cTrader authorisation uses the account-information scope only. Journalit does not request trading permission, and your provider tokens stay on Journalit's encrypted backend rather than in the Obsidian plugin.
Connecting, configuring, resuming, and synchronising cTrader require current Journalit Pro and feature access. Existing connections can still be paused, disconnected, or have their cloud data deleted after access ends.
Sign in to the same Journalit account on Journalit.co and in the Obsidian plugin.
Use a cTrader ID that can access the Demo or Live accounts you want to synchronise.
Create or choose the local Journalit accounts that should receive each broker account's trade notes.
No cBot, trading password, or cTrader platform installation is required by Journalit.
Sign in to Journalit.co and open Dashboard → Integrations. Select the cTrader tab, then choose Connect cTrader. Use Connect another cTrader account when you need a separate connection for another cTrader identity.
Review the cTrader authorisation screen and choose the accounts Journalit may access. cTrader returns you to the matching connection card when authorisation finishes.
On the connection card, enable at least one account and choose its initial history:
The plugin also offers Recent 90 days as a convenient start-date choice during initial setup. All available history means the history cTrader currently exposes for that account. It does not guarantee complete account-lifetime history.
After the first successful synchronisation, you can widen the history range on Journalit.co, but you cannot narrow it. Demo and Live accounts remain separate.
In Obsidian, open Journalit settings → Trade Sync → cTrader. Choose a local Journalit account for every enabled cTrader account. You can create a suitable Journalit account from the same panel if needed.
If the same cTrader account is visible through two cTrader connections, only one connection can synchronise it at a time. Journalit shows which connection currently holds it instead of importing the same account twice.
Choose Finish setup and sync. The plugin saves the account assignments, asks the backend for the latest cTrader activity, waits for that work to finish, and writes the available trade notes into this vault.
Journalit continues checking cTrader while Obsidian is closed. The website shows the last successful sync and the next scheduled sync.
Use Sync now on Journalit.co for an immediate cloud update, or Sync in the plugin to update the cloud and then write notes into the current vault.
While the plugin is open, it checks for pending trade projections and writes the notes that are ready for this vault.
Incremental syncs overlap recent history, and periodic full checks catch older provider corrections without silently treating incomplete history as complete.
The first backfill retrieves the history selected for each account. Later syncs merge cTrader updates with the provider evidence already stored by Journalit. An open position is not treated as a completed trade. Partial closes, realised costs, and the final close continue updating the same trade lifecycle.
Journalit uses cTrader's accounting values for realised profit, commission, swap, and conversion fees rather than estimating them from chart prices. Broker updates can refresh objective trade fields while preserving your thesis, notes, tags, screenshots, reviews, and other locally owned journal content.
You can assign a cTrader account to a different local Journalit account in the plugin. If trade notes already exist, Journalit asks how to handle them:
Use the new Journalit account for future updates and rewrite eligible existing trade notes to use it.
Save the new assignment without rewriting existing notes immediately. A later broker update to an existing trade can still use the new assignment.
Journalit leaves locally deleted notes and conflicting local changes unchanged. If some eligible note updates cannot finish, the plugin reports how many remain pending. Synchronise again to retry. A failed rewrite does not silently discard the new account assignment or overwrite a conflict.
The plugin shows Restore when cloud trades are available but their projected notes are missing from the vault. Select the intended Journalit account, then restore that broker account. This can recover notes after moving to another vault or when an earlier note write did not finish, without reconnecting the cTrader identity. Notes marked as locally deleted are not restored automatically.
Restore and explicit account changes can process pending notes even when that broker account is no longer enabled for new synchronisation. They do not start a new broker-history job for a disabled account.
Return to Dashboard → Integrations → cTrader to manage each connection independently.
Request an immediate cTrader history synchronisation for this connection.
Pause scheduled synchronisation without removing authorisation, then resume it when needed.
Reload connection health, discovered accounts, account selections, and sync timestamps.
Use Reauthorize when access expires, is revoked, or the connection reports that authorisation is required.
Stop future synchronisation and remove this connection's cTrader authorisation. Existing cloud trades and Obsidian notes remain.
Remove cloud data contributed by this connection. Obsidian notes are not deleted.
Disconnect and Delete cloud data are different
Disconnect removes authorisation but preserves the connection's existing cloud trades. Delete cloud data removes connection-owned cloud provenance and trades that have no other active source. Shared execution evidence and audit records can remain under Journalit's retention rules. Neither action deletes notes from your vault.
See the Privacy Policy for the server-side retention distinction.
