Project and website
2When I run it
Runs only when a project member chooses Run now.
When the website publishes
Runs after this project's Web Studio publish operation succeeds.
IDENT.INK
IDENT.INK
IDENT.INK PRODUCT GUIDE
01 · START
Custom mode replaces the premade suite view for that project while it is active. It does not delete premade records. The visual workflow builder is the permanent foundation of Custom mode and cannot be accidentally disabled.
The left library adds blocks. The centre canvas shows their execution order. The right inspector edits the selected block. Drag blocks to reorder them on desktop, or use Move up and Move down on touch devices.
02 · WHEN EVENTS
Runs only when a project member chooses Run now.
Runs after this project's Web Studio publish operation succeeds.
A new Workroom task was saved.
A task title, owner, date, priority or status changed.
A task moved into Done.
A task moved into Blocked.
A task was removed from the active board.
A project note was saved for the first time.
An existing note was edited.
A note became pinned.
A note was removed.
A validated Workroom link was saved.
A saved link was edited.
A link was removed.
A new project invitation was created and emailed.
An invited user accepted and became active.
An owner or admin changed a project role.
A member lost access to the project.
A recurring recipient payment plan was saved.
Its amount, schedule or state changed.
A recurring plan was removed.
Stripe Connect confirmed recipient onboarding.
A scheduled payment succeeded.
A payment failed or requires further Stripe action.
A payout was drafted without moving money.
A permitted member approved a draft.
Stripe confirmed the transfer payment.
The transfer could not complete or needs action.
A new project collection was created.
A collection was removed.
A document was created, updated or deleted. Filter on operation to narrow it.
A validated document was stored.
A document update succeeded.
A document was soft-deleted.
A new scoped database key was issued.
A database key lost access.
03 · FILTERS
Filters read values from the event payload using a dot path. For a task event, examples include task.priority, task.status and task.assignee. Database events expose values such as operation, collectionId and documentId.
Multiple filters currently use AND logic, so every filter must pass. “Is one of” accepts comma-separated values. Numeric comparisons reject non-numeric event values instead of guessing.
04 · ACTIONS
Choose its title, details, starting status, priority, assignee label and due-date offset.
Set the title and body, and decide whether the note should be pinned.
Store a labelled HTTPS resource in a chosen project category.
Change the status and priority of the task supplied by a task event.
Send to an active project member after email automation is unlocked.
Send bounded JSON to a founder-reviewed HTTPS integration. The response is never executed.
Actions run from top to bottom. Drag them on the canvas to change the order. A failed action stops that run and records a failed result rather than pretending the workflow completed. The project limits each workflow to 20 filters and 20 actions, and each project to 250 saved workflows.
The triggering-task action needs a task event containing a task ID. Running it manually without a task safely fails and records the reason.
05 · EMAIL AND OPTIONAL TOOLS
The founder account includes unlimited workflow email. Other project owners can unlock 250 monthly sends for £1.50 per month. Extra one-time packs are 250 credits for £1.50, 1,000 for £5, or 2,500 for £10.
The monthly allowance is used first. Extra credits are used only after it runs out. If delivery fails after a credit is reserved, the credit is returned. Recipients must be active members of the same project.
Only founder-reviewed HTTPS services appear. Events contain bounded JSON. Connections cannot download or execute programs, follow unsafe redirects, access internal addresses, or turn a response into code.
Enabling payroll, payout or IdentDB tools adds their real event blocks to the When catalogue. Payment events report state changes, but money still follows Stripe verification, approval and idempotency controls.
06 · CONTROL AND SAFETY
Rules, runs, records and integrations are scoped to the project that owns them. Normal project permissions control who can read or change workflows.
Creating, editing and deleting rules writes an audit record. Each run records its trigger, result, completed actions and bounded error message.
Task, note, link, rule, filter, action and email limits are enforced on the server, not trusted to the browser.
Clear board affects the current canvas. Delete workflow removes the saved workflow being edited. Delete all requires confirmation and affects only this project.
07 · RECIPES
When a task is created → only if task.priority equals urgent → create a pinned note for the project.
When payroll needs attention → create an urgent task with Finance as the assignee → email an active project member.
When any document changes → only if operation is one of updated, deleted → send a verified API event.
When a task completes → save an evidence link → create the next review task due in seven days.
When a member joins → create an onboarding task assigned to the project team.
08 · TESTING AND HELP
For account, billing or production problems, use Ident.ink Support. Never include passwords, passkeys, complete payment details, API secrets or environment configuration in a ticket.