Two-way sync
Pushing work back out to the tools it came from — and what not to enable.
By default, integrations bring work in. Two-way sync also pushes it back out: a task created in Nalaras becomes a GitHub issue, a Trello card or a Notion page.
It is off until you turn it on
Outbound sync is off for every connection until someone enables it, per integration, per project. Nothing leaves your workspace by accident.
Toggle it on the integration's card in Integrations.
What goes out
- New tasks become an issue, card or page.
- Edits to a synced task update the copy.
- Comments are posted across.
Nothing loops
A task that came in from GitHub is never pushed back to GitHub, and an issue Nalaras created is not re-ingested as a new task. Nalaras records the link between the two and checks it in both directions, so items cannot multiply.
Before you enable it
Internal-only tasks are not pushed. A task with client visibility off stays in Nalaras.
But a task that was mirrored out while it was visible and marked internal afterwards keeps the copy already sitting on the external board. Nothing further is pushed to it, but withdrawing what is already there means deleting the card or issue yourself.
Worth asking once, before turning this on: who can see the destination board? An external board is a second audience with its own access list, and it is often wider than the project's.
If Trello stops syncing
Trello signs its webhooks over the callback URL, so a change to where Nalaras is hosted invalidates every webhook registered before it. The fix is to disconnect and reconnect the board, once per board.