Skip to main content

SyncNow Execution Agent

What Is the SyncNow Execution Agent?​

The SyncNow Execution Agent lets you manage SyncNow itself through natural language conversations instead of clicking through the admin UI.

From Dashboard to Chat

No more navigating through complex admin panels. Just ask what you need!

Manage SyncNow by asking:

"Show me all active sync processes"
"What sync errors occurred today?"
"Create a mapping between Jira and Azure DevOps"
"Pause the billing sync process"

The Execution Agent understands SyncNow operations and executes admin tasks securely.

Screenshot placeholder: Shows a conversation with the Execution Agent in Slack

Why Use the Execution Agent?​

⚡ Faster Administration​

  • No navigating through menus
  • Get status and diagnostics instantly
  • Execute common tasks in seconds

🔍 Intelligent Troubleshooting​

  • Ask about errors in natural language
  • Get diagnostic information with context
  • Suggested fixes based on error patterns

📱 Mobile-Friendly​

  • Manage SyncNow from Slack/Teams/Discord
  • No need to access the full UI
  • Quick status checks from anywhere

🤖 Automation-Ready​

  • Scriptable via MCP protocol
  • Integrate with monitoring tools
  • Automated health checks

How It Works​

Step-by-Step Execution

1. You ask in natural language
"Show sync process status"

2. Execution Agent understands your intent

  • 🎯 Operation: Get status
  • 📝 Entity: Sync processes
  • 🔍 Filter: All active

3. Operation executes securely

  • ✅ Validates your permissions
  • 📡 Calls SyncNow API
  • ⚙️ Retrieves data from SyncNow Core

4. You get a formatted answer
📊 Table of active sync processes with real-time status

Image placeholder: Detailed flow diagram showing the full execution pipeline

Capabilities​

Four Core Operation Types

The Execution Agent supports four categories of operations with different permission requirements.

Status & Monitoring​

Get process status:

"Show sync process status"
"List all active sync processes"
"What processes are running right now?"

Check for errors:

"What sync errors occurred today?"
"Show failed sync items from the last hour"
"Any sync warnings in the last 24 hours?"

View history:

"Show sync history for the last week"
"When did the billing sync last run?"
"What items were synced in the last hour?"

Permission Required: 🔓 Viewer (Read-only)

Screenshot placeholder: Real-time monitoring dashboard showing process status

Capability Matrix​

Operation CategoryViewerOperatorPower UserAdministrator
📊 Status & Monitoring✅✅✅✅
⚙️ View Configuration✅✅✅✅
🎮 Process Control❌✅✅✅
🔧 Modify Configuration❌❌✅✅
🔐 System Settings❌❌❌✅

Configuration Management​

View mappings:

"Show all mappings"
"List mappings between Jira and Azure DevOps"
"What fields are mapped in the billing sync?"

View connectors:

"List all connectors"
"Show Jira connector configuration"
"What connectors are currently enabled?"

View sync processes:

"Show all sync processes"
"List processes using the Jira connector"
"What processes sync from Azure DevOps to ServiceNow?"

Process Control​

Start/stop/pause processes:

"Start the billing sync process"
"Pause the Azure DevOps sync"
"Stop all sync processes"

Trigger manual syncs:

"Run the Jira-to-Azure sync now"
"Force sync for item JIRA-123"

Troubleshooting​

Diagnose issues:

"Why did sync fail for item ABC-123?"
"Show error details for the last failed sync"
"What's causing sync errors in the billing process?"

Get recommendations:

"How can I fix the 'field not found' error?"
"What permissions do I need to create a mapping?"
"Troubleshoot slow sync performance"

Configuration Creation (Advanced)​

Create mappings:

"Create a mapping from Jira to Azure DevOps"
"Map Jira bug to Azure DevOps work item"

Configure fields:

"Map Jira 'Summary' field to Azure 'Title' field"
"Add custom field mapping for 'Customer Impact'"

Operations Reference​

Monitoring Operations​

Command PatternWhat It DoesExample
Show process statusLists sync processes with current status"Show sync process status"
List errorsShows sync errors with filters"What errors occurred today?"
View historyDisplays sync execution history"Show sync history for last week"
Get diagnosticsDetailed diagnostic info"Diagnose sync performance issues"

Configuration Operations​

Command PatternWhat It DoesExample
Show mappingsLists field and entity mappings"Show all mappings"
List connectorsShows configured connectors"List all connectors"
View sync processesDisplays sync process definitions"Show all sync processes"
Get mapping detailsDetailed mapping configuration"Show field mappings for billing sync"

Control Operations​

Command PatternWhat It DoesExample
Start processStarts a sync process"Start the billing sync"
Stop processStops a running sync process"Stop the Jira sync"
Pause processPauses a sync process"Pause the Azure DevOps sync"
Resume processResumes a paused process"Resume the billing sync"
Trigger syncManually triggers sync execution"Run the Jira-to-Azure sync now"

Troubleshooting Operations​

Command PatternWhat It DoesExample
Diagnose errorAnalyzes specific error"Why did sync fail for ABC-123?"
Get recommendationsSuggests fixes"How do I fix 'field not found'?"
Check permissionsValidates permission setup"Do I have permission to create mappings?"
Performance analysisAnalyzes sync performance"Why is sync slow?"

Example Scenarios​

Real-World Workflows

These scenarios show how the Execution Agent helps with daily SyncNow management tasks.

Scenario 1: Morning Health Check ☀️​

Conversation:

You: "Show sync process status"

Execution Agent:

📊 **Active Sync Processes: 3**

| Process              | Status  | Last Run        | Items Synced | Errors |
|----------------------|---------|-----------------|--------------|--------|
| Jira → Azure DevOps  | ✅ Running | 2 minutes ago   | 47           | 0      |
| ServiceNow → Jira    | ⏸️ Paused  | 1 hour ago      | 12           | 0      |
| Azure → ServiceNow   | ✅ Running | Just now        | 8            | 0      |

✅ All processes healthy | ⏱️ Response time: 0.8s

You: "Any errors today?"

Execution Agent:

✅ **No sync errors today**

Last error was yesterday at 14:32:
- 🎫 Item: JIRA-4567
- ❌ Error: Field mapping not found for 'CustomField_123'
- ✅ Status: Resolved
- 🔧 Fixed by: admin@company.com

Screenshot placeholder: Complete health check dashboard showing status, history, and recommendations

Scenario 2: Troubleshooting a Failed Sync 🔍​

Conversation:

You: "What sync errors occurred in the last hour?"

Execution Agent:

⚠️ **3 errors in the last hour:**

1. **JIRA-789** (5 minutes ago)
   - ❌ Error: Authentication failed for Azure DevOps connector
   - 🔄 Sync Process: Jira → Azure DevOps
   - 🎯 Impact: Blocking 2 other items
   
2. **JIRA-790** (5 minutes ago)
   - ❌ Error: Same as JIRA-789 (duplicate)
   - 🔄 Sync Process: Jira → Azure DevOps
   
3. **SNOW-123** (22 minutes ago)
   - ❌ Error: Required field 'Priority' missing in target system
   - 🔄 Sync Process: ServiceNow → Jira
   - ℹ️ Different issue (field mapping)

💡 Tip: Focus on JIRA-789 first—fixing it will resolve JIRA-790 too!

You: "Why did JIRA-789 fail?"

Execution Agent:

🔍 **JIRA-789 Sync Failure Analysis**

**Error**: Authentication failed for Azure DevOps connector

**Root Cause**: Azure DevOps Personal Access Token (PAT) expired
- Token expired: February 20, 2026 at 23:59
- Current time: February 21, 2026 at 09:45
- Time expired: 9 hours ago

**Impact**: 🚨 All Jira → Azure DevOps syncs are failing
- Affected items: 2 (JIRA-789, JIRA-790)
- Queue blocked: Yes
- Estimated items pending: ~15

**Recommended Fix**:
1. ⚙️ Go to Connectors → Azure DevOps
2. 🔑 Update the PAT with a new token
3. ✅ Test connection
4. 🔄 Retry failed items (automatic)

**Related Items**: JIRA-790 (same root cause)

💡 Need help generating a new PAT? [Azure DevOps PAT Guide →](#)

You: "Retry sync for JIRA-789"

Execution Agent:

⚠️ **Cannot retry: Authentication still failing**

The Azure DevOps connector is still unable to authenticate.

**Next Steps:**
1. Update the connector PAT first
2. Test the connection
3. Then retry will work automatically

Would you like me to:
- [Show how to update PAT](#)
- [Test connection now](#)
- [Show connector settings](#)

After fixing:

You: "Test Azure DevOps connection"

Execution Agent:

✅ **Connection Test Successful!**

Connector: Azure DevOps
Status: ✅ Connected
Response Time: 245ms
Token: Valid (expires in 89 days)

**Auto-Retry Results:**
- JIRA-789: ✅ Synced successfully
- JIRA-790: ✅ Synced successfully
- Queue: ✅ All pending items processing

🎉 All clear! Sync is back to normal.

Screenshot placeholder: Step-by-step troubleshooting wizard with diagnostics and recommendations

Scenario 3: Creating a New Mapping​

You: "Show all mappings"

Execution Agent:

**5 Active Mappings:**

1. **Jira Bug → Azure DevOps Bug**
   - Direction: Bidirectional
   - Fields: 12 mapped
   - Active: Yes
   
2. **Jira Story → Azure DevOps User Story**
   - Direction: Jira → Azure
   - Fields: 15 mapped
   - Active: Yes
   
3. **ServiceNow Incident → Jira Bug**
   - Direction: ServiceNow → Jira
   - Fields: 8 mapped
   - Active: Yes

...

You: "Show field mappings for 'Jira Bug → Azure DevOps Bug'"

Execution Agent:

**Field Mappings: Jira Bug → Azure DevOps Bug**

| Jira Field       | Azure DevOps Field | Transform       | Direction     |
|------------------|--------------------|-----------------|---------------|
| Summary          | Title              | Direct          | Bidirectional |
| Description      | Description        | HTML → Markdown | Bidirectional |
| Priority         | Priority           | Value Map       | Bidirectional |
| Status           | State              | Value Map       | Bidirectional |
| Assignee         | Assigned To        | User Map        | Bidirectional |
| Labels           | Tags               | Array           | Bidirectional |
| CustomField_001  | CustomField.Impact | Direct          | Jira → Azure  |
...

You: "Add custom field mapping: Jira 'Customer Impact' to Azure 'Business Value'"

Execution Agent:

✅ Field mapping added successfully

**New Mapping:**
- Jira Field: Customer Impact (CustomField_002)
- Azure Field: Business Value (CustomField_004)
- Transform: Value Map
- Direction: Bidirectional

**Next Step**: Configure value mappings?
(e.g., High → 3, Medium → 2, Low → 1)

Permissions & Security​

Who Can Use the Execution Agent?​

Access is controlled by SyncNow role-based permissions:

RoleMonitoringConfigurationProcess ControlTroubleshooting
Administrator✅✅✅✅
Power User✅✅✅✅
Operator✅❌✅✅
Viewer✅❌❌❌

Operation-Level Permissions​

Fine-grained control over specific operations:

Read Operations (monitoring, viewing config):

  • Requires: syncnow.read permission

Write Operations (creating/modifying config):

  • Requires: syncnow.write permission

Control Operations (start/stop/pause processes):

  • Requires: syncnow.control permission

Administrative Operations (system settings):

  • Requires: syncnow.admin permission

Audit Logging​

All Execution Agent operations are logged:

  • Who executed the command
  • What operation was performed
  • When it happened
  • Result (success/failure)
  • IP address and session info

Access logs via:

"Show my recent admin actions"
"Who modified the billing sync mapping?"
"Audit log for the last 24 hours"

Best Practices​

1. Use Descriptive Names​

✅ Good:

"Show status for the 'Billing Sync' process"
"Pause the 'Jira-to-Azure DevOps Bug Sync'"

❌ Avoid:

"Show status for sync 1"
"Pause that process"

2. Be Specific with Time Filters​

✅ Good:

"Show errors from the last hour"
"Sync history for yesterday"

❌ Avoid:

"Show recent errors" (vague)

3. Ask Follow-Up Questions​

Build on previous context:

You: "Show sync errors today"
Agent: [Shows 3 errors]

You: "Diagnose the first one"
Agent: [Analyzes JIRA-789 error]

You: "How do I fix it?"
Agent: [Provides solution]

4. Use Process Names​

If you have multiple processes syncing the same systems:

"Status for the 'Bug Sync' process"
"Pause 'Story Sync' but keep 'Epic Sync' running"

Performance Considerations​

Caching​

The Execution Agent caches:

  • Connector configurations (5-minute TTL)
  • Mapping definitions (5-minute TTL)
  • Process status (30-second TTL)

Cache invalidation happens automatically on configuration changes.

Rate Limiting​

To protect system performance:

  • Max 60 requests per minute per user
  • Max 10 concurrent process control operations
  • Diagnostic queries may take longer (up to 30 seconds)

Batch Operations​

When possible, use batch commands:

✅ Efficient:

"Show status for all sync processes"

❌ Less efficient:

"Status for Jira sync"
"Status for Azure sync"
"Status for ServiceNow sync"

Troubleshooting Guide​

Common Issues​

Issue: "I don't have permission to execute this command"

Solution:

  1. Check your SyncNow role (Viewer can only monitor, not control)
  2. Ask your administrator for the appropriate permission
  3. View your permissions: "What permissions do I have?"

Issue: "The sync process is running slow"

Solution:

"Diagnose sync performance for [process name]"

The agent will analyze:

  • Item volume
  • Network latency to connectors
  • API rate limiting
  • Complex field transformations
  • Suggested optimizations

Issue: "Sync failed with 'authentication error'"

Solution:

  1. Check connector credentials: "Show connector configuration for [system]"
  2. Test connection: "Test connection for [connector name]"
  3. Update credentials if expired
  4. Retry failed items

Issue: "Field mapping not found error"

Solution:

"Show field mappings for [mapping name]"
"What fields are mapped?"

Then add missing mapping:

"Add field mapping: [source field] to [target field]"

Advanced Features​

Scheduled Queries​

Set up recurring status checks:

"Send me a daily summary of sync errors at 9 AM"
"Alert me when sync process fails"
"Weekly report of sync volume and performance"

Conditional Actions​

Create automated responses:

"If sync errors exceed 10 per hour, pause the process and alert me"
"Auto-retry failed items after 5 minutes"

Custom Dashboards​

Build personalized views:

"Create a dashboard showing:
 - Active process status
 - Error count (last 24h)
 - Sync volume (last 7 days)
 - Top 5 problematic items"

API Reference​

For developers integrating with the Execution Agent via MCP:

Endpoints​

Status Operations:

  • agent.syncnow.getProcessStatus
  • agent.syncnow.listErrors
  • agent.syncnow.getHistory

Configuration Operations:

  • agent.syncnow.listMappings
  • agent.syncnow.getMappingDetails
  • agent.syncnow.listConnectors

Control Operations:

  • agent.syncnow.startProcess
  • agent.syncnow.stopProcess
  • agent.syncnow.pauseProcess
  • agent.syncnow.triggerSync

See MCP Integration Guide →

Next Steps​

Quick Reference​

Common Commands​

Monitoring:

"Show sync process status"
"What errors occurred today?"
"Show sync history for last week"

Configuration:

"Show all mappings"
"List all connectors"
"Show field mappings for [mapping name]"

Control:

"Start the [process name] sync"
"Pause [process name]"
"Stop all sync processes"

Troubleshooting:

"Why did sync fail for [item ID]?"
"Diagnose [process name] performance"
"Show error details for the last failed sync"

Related Documentation: