Notification and auto-link automation

Not every automation needs an external webhook. Usable also provides released workspace email notification rules and tag-driven auto-link rules for specific collaboration and organization workflows.

Email notification rules

Where enabled, workspace settings can expose email rules for events such as fragment creation and updates.

A safe setup:

1. Open workspace settings.
2. Create a clearly named notification rule.
3. Select only required event types.
4. Add intentional recipient addresses.
5. Apply fragment-type filters where exposed.
6. Save and test with a low-risk fragment.
7. Review message content and recipient visibility.
8. Deactivate obsolete rules.

Notification emails can expose titles, summaries, or content snippets. Review private and public workspace audiences before adding broad recipient lists.

Notification troubleshooting

Usable v1.189.1 made delivery-event/audit writes best-effort so an audit timeout does not by itself block email delivery.

If history appears incomplete:

• check the recipient mailbox;
• inspect suppression state;
• confirm rule and fragment-type filters;
• verify the approximate event time;
• do not conclude the email was skipped solely from a missing audit row.

Reduce noise by narrowing event types, filters, and recipients rather than teaching users to ignore messages.

Auto-link rules

Auto-link rules watch tags in a source workspace and create symlink children in another workspace. They are appropriate for controlled knowledge routing, not arbitrary workflow execution.

Released fields include:

• matchMode: any or all;
• 1–25 normalized tags;
• target workspace ID, different from the source;
• enabled state.

Owners/collaborators need appropriate access in both source and target workspaces.

Preview before enabling

Use preview to inspect:

• total matched;
• links that would be created;
• already-linked fragments;
• skipped records;
• failures.

Review titles, tags, source and target visibility, and whether public/private boundaries are appropriate. A broad any rule can route much more content than expected.

Reprocess existing fragments

Reprocess applies a saved rule to existing matching fragments. Preview first and review row actions such as create, already linked, skipped, or failed.

Released safety behavior includes:

• cycle checks for enabled rules;
• skipping fragments already created as symlink children;
• no recursive linking of symlink children;
• a processing/background-batching result when more than 50 child creations would be required synchronously.

Do not repeat a processing reprocess immediately; verify resulting state before retrying.

Maintain rules

• Disable a rule before major review.
• Keep tags stable and documented.
• Re-preview after changing tags, match mode, or target.
• Remove stale symlinks deliberately.
• Verify source updates remain understandable in target context.
• Delete rules only after checking downstream expectations.

A symlink child is a maintained relationship, not an independent copy to edit as though it were the source.

Hosted Zone boundary

For Leaf-backed workspaces, collection and symlink tools route on the Leaf data plane in the released Hosted Zone model. Cloud must not become a fallback for private fragment data.

Confirm both workspaces' placement and access before creating cross-workspace rules. Keep the dedicated Hosted Zones guidance as the source for routing details.

Choose the right automation

• Webhook: external machine action.
• Email rule: human notification.
• Auto-link rule: cross-workspace knowledge relationship.
• Direct REST/MCP: deterministic or agent-selected operation.

Do not chain mechanisms without documenting ownership, deduplication, and failure handling.

Related pages

• Fragment symlinks
• Workspace members and invitations
• Webhooks and automation in Usable
• Hosted Zones and MCP troubleshooting