Knock

Communication

Neotask builds and manages your Knock notification infrastructure through OpenClaw — 47 actions for creating workflows, managing users, and orchestrating notifications through conversation.

What You Can Do

With 47 actions, Neotask's Knock integration through OpenClaw provides complete programmatic control over your notification orchestration platform.

| Area | Key Actions | What Gets Automated |

|------|-------------|---------------------|

| Workflows | list, get, trigger, create, create schedule, manage steps (email, delay, batch, in-app, push, SMS, chat) | Build and trigger notification workflows through conversation |

| Workflow Steps | createOrUpdate for all 7 channel types | Architect multi-channel notification sequences |

| Users | get/create/update users, get preferences/messages | Manage user notification profiles programmatically |

| Objects | list, get, create/update, subscribe/unsubscribe users | Manage non-user recipients and group subscriptions |

| Messages | get, get content, delivery logs, events | Monitor notification delivery and debug failures |

| Tenants | list, get, create/update, delete tenants | Manage multi-tenant notification routing |

| Email Layouts | list, get, create/update layouts | Maintain notification email templates |

| Guides | list, get, create/update guides | Manage in-app guidance content |

| Environments | list environments | Navigate staging and production environments |

| Commits | list, commit all, promote all | Manage notification infrastructure deployments |

Every action runs autonomously or requires your approval — you decide.

Try Asking

  • "Create a new notification workflow called 'trial-ending' with an email 3 days before trial end and an in-app message on the final day"
  • "Trigger the welcome-sequence workflow for user ID usr_12345 with their name and account details"
  • "What notifications did user usr_abc123 receive in the last 7 days and were they all delivered?"
  • "Commit all pending Knock changes and promote them to production"
  • "Set up user preferences for new signups: email enabled, SMS disabled by default"
  • "Create a batch step in our digest workflow that groups notifications every 24 hours"
  • "List all active workflows and show me which ones have been triggered in the last 30 days"
  • "Get the delivery logs for the last failed notification in our onboarding workflow"

    • Pro Tips

  • Enable approval gates on commitAllChanges and promoteAllCommits — promoting notification changes to production affects all users and deserves human sign-off.
  • Connect Knock with your user database in an app group: when a user's status changes (trial to paid, active to churned), agents automatically trigger the appropriate Knock workflow.
  • Multi-agent teams can build notification systems: one agent designs the workflow structure, another creates the message content, and a third configures delivery preferences by user segment.
  • Schedule a weekly notification audit that checks delivery rates, open rates, and unsubscribe trends across all active workflows — catch notification fatigue early.
  • Use Knock's tenant system for B2B notification routing — agents can configure per-tenant notification preferences and branding automatically when new enterprise customers onboard.

    • Works Well With