Skip to main content

// part of Anor

Connectors you can trust

Versioned plugins for Anor. Each declares triggers and actions. Workflows compose them. The run engine enforces safety and audit regardless of vendor.

// connectors

CygNet
Shipping
SCADA connector. Preview/apply writes, device clone, bulk updates, alarm workflows, and ODBC query designer.

Triggers

  • · Alarm queue update
  • · Scheduled poll
  • · Manual run

Actions

  • · Query points and facilities
  • · Clone devices and bulk updates
  • · Ack alarms and investigate trends
Microsoft Teams
Shipping
Notify channels and people, collect approvals, and keep operational updates in the same thread your team already uses.

Triggers

  • · Workflow step
  • · Approval request
  • · Manual run

Actions

  • · Post channel message
  • · Notify a user
  • · Request approval
O365 Email
Shipping
Microsoft 365 mailbox connector. Read messages, extract attachments, classify intent, and route operational mail into workflows.

Triggers

  • · New message
  • · Folder match
  • · Scheduled inbox scan

Actions

  • · Read messages and attachments
  • · Classify and route
  • · Send or reply
Azure DevOps
Shipping
Work item connector. Create and update tickets, add diagnostic comments, and keep triage state in the board your team already runs.

Triggers

  • · New or updated work item
  • · Workflow step
  • · Manual run

Actions

  • · Create or update work items
  • · Add comments and findings
  • · Assign and route ownership
Snowflake
Shipping
Warehouse and analytics queries inside governed operational workflows.

Triggers

  • · Workflow step
  • · Scheduled query

Actions

  • · Run parameterized query
  • · Export results to run log
Ignition MCP
Shipping
Ignition via MCP. Bring Ignition tools into the same run engine, safety model, and audit trail as your other connectors.

Triggers

  • · Workflow step
  • · Manual run

Actions

  • · Call Ignition MCP tools
  • · Pass structured results to later steps
Third-party MCP servers
Shipping
Point Anor at any MCP server and use its tools as connector steps — same composition, gates, and audit as first-party connectors.

Triggers

  • · Workflow step
  • · Manual run

Actions

  • · Discover MCP tools
  • · Invoke tool with schema inputs
  • · Capture tool output in the run log

// connector framework

Manifest contract

Name, version, auth, capabilities, actions with JSON Schema, per-action safety (read-only, preview/apply, confirm required).

Run engine

Workflow state, pause/resume, human decision nodes, prompt steps, changesets, and audit — owned by Narya, not each connector.

WAIS retrieval

Site conventions, lessons, and golden rules scoped by connector, workflow, and skill during every run.