Keep your board in the conversation.
Create issues with assignee and priority, add comments, and move issues through supported transitions. Review the proposed change before confirming. Jira project permissions still apply.
Private pilotFor founders and team leads
Your team already said what needs doing.
NOD turns requests from your team’s WhatsApp groups, Slack channels and Gmail folders into tasks and prepared actions — then asks for your approval before anything changes in Jira, GitHub or your CRM.
Supported changes wait for confirmation before they run.
Launch teamWhatsApp group · linked to NOD
AS
Login still fails on iPhone. One more fix before we ship.
MK
Create a Jira issue in NOD: Fix login on iPhone. Assign to Alex, priority High.
Created NOD-142 · Fix login on iPhone. Assigned to Alex, priority High.
NOD
Listening for a supported request in linked conversations.
Request understood
- ActionCreate Jira issue
- ProjectNOD
- TitleFix login on iPhone
- AssigneeAlex Shah
- PriorityHigh
Prepared Jira issueNothing has been sent yetApproved by the founder
Fix login on iPhone
- Destination
- Jira · NOD project
- Assignee
- Alex Shah
- Priority
- High
- Requested by
- Maya · Launch team
Jira · NOD-142Created
Fix login on iPhone
- Assignee
- Alex Shah
- Priority
- High
Confirmation sent to Launch team
Maya asks for a Jira issue in the team’s WhatsApp group.
Works with
- Slack
- Gmail
- Jira
- GitHub
The gap
Decisions happen in chat. The follow-through gets copied somewhere else — by hand, one message at a time.
Today
- Read the message
- Open the right tool
- Re-enter the details
- Tell the team
With NOD
- Say it in the chat
- Review, then approve
How it works
Watch the whole handoff.
Four short films follow supported workflows with sample data, from the first message to the recorded result.
Playback is unavailable. The written walkthrough is below.
- Request“Create a Jira issue in NOD: Fix login on iPhone. Assign to Alex, priority High.”
- UnderstoodCreate issue · NOD project · Alex · High
- PreparedFix login on iPhone → Jira / NOD. Nothing has been sent yet.
- ApprovedThe workspace founder approves the request in NOD.
- DoneJira creates NOD-142. NOD confirms it in the original chat.
Read the walkthrough
- Maya asks for a Jira issue in the Launch team WhatsApp group.
- NOD identifies the action, project, title, assignee and priority.
- NOD prepares the issue for review. Nothing has been sent yet.
- The workspace founder reviews the request in NOD and approves it.
- Jira creates NOD-142, and NOD confirms it in the original chat.
Playback is unavailable. The written walkthrough is below.
- SourcesA team chat, Jira issue NOD-142 and a CodeFlow update you can access.
- Question“What’s happening with authentication?”
- AnswerThe release is waiting on review. Alex owns the fix, NOD-142. Next: review the submitted update.
- ReferencesEach line links to the source it came from.
Read the walkthrough
- NOD brings together context you can access: a team chat, a Jira issue and a CodeFlow update.
- A teammate asks what is happening with authentication.
- NOD answers in three short lines.
- Each line links to the source it came from, so the teammate can check the details.
Playback is unavailable. The written walkthrough is below.
- Request“Move NOD-142 to In Progress.”
- Exact previewNOD-142 · To do → In Progress · Jira, NOD project · requested by Maya.
- ConfirmationConfirmed once. Confirmations expire after 15 minutes.
- RecordedJira applies the transition. NOD records the result.
Read the walkthrough
- A manager asks NOD to move NOD-142 to In Progress.
- NOD shows the exact change, the destination and who asked.
- The manager confirms. The confirmation runs once and expires after 15 minutes.
- Jira applies the transition, and NOD records the result.
Playback is unavailable. The written walkthrough is below.
- SubmittedBranch fix/auth-redirect · commit 8c4a2f1, sent from CodeFlow.
- ReviewThe founder reviews that exact commit in NOD.
- ApprovedApproval applies to the reviewed commit only.
- WorkflowThe configured GitHub workflow continues. Repository checks still apply.
Read the walkthrough
- A developer submits a pushed branch and commit from CodeFlow.
- The founder reviews that exact commit in NOD.
- The founder approves the reviewed commit.
- The configured GitHub workflow continues, subject to repository checks, and NOD records the outcome.
What NOD handles
The follow-through, prepared.
NOD connects the places your team talks with the places work gets recorded. Everything here is available today; some of it needs setup by your workspace administrator.
- 01Supported
Tasks from the conversation
NOD picks up tasks from the Gmail folders and Slack channels you select, and from explicit task and reminder requests in linked WhatsApp groups — with the source attached.
- 02Supported
Jira, from a sentence
Create issues with an assignee and priority, add comments and move issues through supported transitions. Each change is prepared for review, and Jira project permissions still apply.
- 03Supported
Answers with their sources
Ask about a project and get a short summary of the work, messages and development updates you can access, with references you can check.
- 04Setup required
Development handoffs
Developers submit a pushed commit from CodeFlow. A founder reviews that exact commit, and approval can start configured pull-request and merge steps, subject to repository checks. NOD doesn’t write the code.
- 05Feature gated
A pipeline that stays current
Track deals in Revenue Sync. With administrator setup and stage mappings, pull Salesforce Opportunities or HubSpot Deals into NOD and push reviewed changes back.
- 06Supported
Client updates, on purpose
Internal discussion stays internal. Prepare a client update, review what it shares and publish it to a linked client workspace. Client questions are answered from published items only.
Integrations
Connected to the tools you already use.
Start with what matters to your team. Availability depends on your workspace’s setup, permissions and plan.
Where requests start
NODUnderstands · prepares · asksWhere work is recorded
WhatsApp → Jira. A linked conversation can prepare a supported Jira request for review. Workspace and project permissions apply.
Example routes, not every-to-every automation. Each depends on setup, permissions and enabled features.
A clear path from commit to review.
Submit development updates from CodeFlow and review the exact pushed commit. Approval can start configured pull-request and merge actions, subject to repository checks. NOD does not generate code in this workflow.
Milestones that stay with the customer.
Revenue Sync tracks NOD deals and recognized milestones from authorized WhatsApp conversations and selected Gmail sales folders. Share relevant progress while keeping email bodies private.
Salesforce Opportunities. HubSpot Deals.
Explicit pull and push workflows support mapped deal stages after review. They require OAuth configuration, feature access, and stage mappings. Contact synchronization and Zoho are not available.
NOD is in private pilot. A listed connector does not mean it is enabled in every workspace.Control
AI prepares the action. You make the call.
Supported interactive changes stop for review. You see the exact change, where it’s going and who asked — then you decide.
- 1
The exact change
See what will change and where it goes before you confirm it.
- 2
Used once, then it expires
Confirmations run once and expire after 15 minutes. Changed or expired requests can’t run.
- 3
Roles decide what’s possible
Workspace membership, group access and connected-tool permissions determine the actions available to each person.
- 4
You choose the sources
Select the Gmail folders and Slack channels NOD reads. Manage connected accounts and review recorded activity.
Review before sendingExampleMove NOD-142 to In Progress
ChangeTo do In Progress1
DestinationJira · NOD project
Requested byMaya · Launch team
ConfirmationSingle use · expires in 15 min2
Scheduled reports and reminders you’ve already set up continue under their saved settings. NOD is private-pilot software; review its data-use and participation terms before joining.
Questions
Clear from the beginning.
What exactly does NOD do?
NOD connects workplace conversations with the tools your team uses. It identifies tasks, summarizes relevant work and prepares supported Jira, CRM and development actions, so you spend less time moving information between applications.
Does NOD replace Slack or Jira?
No. Your connected tools stay part of the workflow. NOD connects their context and prepares updates, while you keep using your existing channels, projects and repositories.
Which applications does NOD support?
Implemented connections include Slack, Gmail, WhatsApp, Jira, and GitHub with CodeFlow. Revenue Sync is NOD’s built-in pipeline. Salesforce Opportunity and HubSpot Deal synchronization require administrator configuration and enabled features. Zoho and contact sync are not available.
Can NOD make changes without my approval?
Supported interactive writes use confirmation workflows. For WhatsApp Jira creation, the founder can review the request in NOD, or the authorized requester can confirm in the source chat. CodeFlow uses approval of the reviewed commit. Automatic task extraction and reports or reminders you already scheduled follow their existing settings; they don’t ask for a new approval on every run.
Do I need technical knowledge?
You can ask questions and describe work in everyday language. Some actions use supported commands, which NOD helps you review. An administrator may need to configure integrations; GitHub and CodeFlow workflows require repository and development setup.
How do I start using NOD?
Create an account, review the private-pilot terms, and set up or join a workspace. Then connect the supported tools available to your workspace. You can start with your own tasks before connecting more services.
Get startedHow is my data used?
NOD processes the content you connect to provide workspace features, including AI-assisted extraction. NOD does not use your content to train AI models. Read the privacy overview and full pilot terms before joining.
Say it once. Approve it. Move on.
Bring your team’s conversations and tools into one reviewed workflow.
Private pilot. You’ll review the pilot terms before entering your workspace.