Nicereply Feedback Router to Teams

What This Agent Does

This workflow automates the collection and distribution of customer feedback from Nicereply, intelligently categorizing responses by sentiment, and delivering organized summaries directly to your Microsoft Teams channel. By running on a scheduled interval, it continuously monitors for new feedback without requiring manual intervention, ensuring your team stays informed about customer satisfaction in real-time.

Key benefits include:

• Automated feedback collection that eliminates manual polling and data gathering
• Intelligent sentiment routing that separates positive, neutral, and negative feedback for targeted team responses
• Real-time team notifications delivered directly to Microsoft Teams, keeping stakeholders informed instantly
• Time savings of 5-10 hours per week by automating what would otherwise be manual feedback review processes
• Improved response times to customer concerns through immediate visibility of negative feedback

Target use cases:

• Customer success teams monitoring satisfaction metrics across products or services
• Support departments tracking feedback quality and identifying improvement areas
• Product teams gathering user sentiment for feature prioritization
• Multi-department organizations needing centralized feedback visibility

Who Is It For

This workflow is ideal for customer-focused organizations of any size that use Nicereply for feedback collection and Microsoft Teams for team communication. It's particularly valuable for:

• Customer Success Managers who need to monitor satisfaction trends without manual data entry
• Support Team Leads coordinating responses to customer feedback across multiple channels
• Product Managers tracking user sentiment to inform development priorities
• Executive Teams requiring regular visibility into customer satisfaction metrics
• Multi-location or remote teams that rely on centralized communication platforms

No advanced technical knowledge is required—if you can configure integrations and understand basic workflow concepts, you can set up this agent successfully.

Required Integrations

Microsoft Teams

Why it's needed: Microsoft Teams serves as the delivery channel for your processed feedback summaries. This integration enables the workflow to send organized, sentiment-categorized messages directly to your team channel, ensuring stakeholders see feedback immediately without checking external systems.

Setup steps:

1. Access your Microsoft Teams workspace and identify the channel where you want feedback delivered (e.g., #customer-feedback or #support-alerts)
2. Navigate to TaskAGI's integration marketplace and search for "Microsoft Teams"
3. Click "Connect" or "Authorize" to initiate the OAuth connection flow
4. Sign in with your Microsoft 365 account when prompted
5. Grant TaskAGI permission to send messages to your Teams channels (you'll see a permissions consent screen)
6. Confirm the connection and return to TaskAGI—your Teams account is now linked
7. In the workflow configuration, select your connected Teams account from the dropdown menu
8. Choose your target channel from the list of available channels in your workspace

How to obtain credentials: You don't need to manually obtain API keys for Teams—the OAuth flow handles authentication automatically. Your Microsoft 365 account credentials are all that's required.

Configuration in TaskAGI: Once connected, the Teams integration appears as a pre-authenticated option in the "Send to Teams Channel" node. Simply select your workspace and channel, and the workflow will have permission to post messages.

Configuration Steps

Node 1: Schedule Trigger (trigger.schedule_interval)

This node determines how frequently your workflow runs and checks for new feedback.

Configuration parameters:

• Interval Type: Select hours, days, or weeks based on your feedback volume
• Interval Value: Enter the number (e.g., 1 for every hour, 4 for every 4 hours, 1 for daily)
• Recommended setting: 1 hour for active feedback environments, 4 hours for moderate volume, 1 day for low-volume feedback

Example: If you set interval to 1 hour, the workflow executes every 60 minutes, checking for new Nicereply feedback.

Node 2: Get Nicereply Feedback (core.http_request)

This node retrieves feedback data from your Nicereply account via API.

Configuration parameters:

• URL: https://api.nicereply.com/v1/feedback (or your Nicereply API endpoint)
• Method: GET
• Headers: Include your Nicereply API key:

  Authorization: Bearer YOUR_NICEREPLY_API_KEY
  

• Query Parameters: Add limit=100 and since=LAST_EXECUTION_TIME to fetch only new feedback

How to obtain Nicereply API key:

1. Log into your Nicereply account
2. Navigate to Settings → API & Integrations
3. Click Generate API Key (or copy existing key)
4. Copy the key and store it securely
5. Paste it into the Authorization header above

Node 3: Process Feedback Data (core.function)

This node transforms raw Nicereply data into a structured format your workflow can process.

Configuration:

• Input: Raw feedback array from Node 2
• Function logic: Extract relevant fields:

  - feedback_id
  - customer_name
  - feedback_text
  - sentiment_score (numerical value)
  - timestamp
  

• Output: Structured array of feedback objects

Example output structure:

{
  "feedback_id": "12345",
  "customer_name": "Jane Smith",
  "feedback_text": "Great product, very satisfied!",
  "sentiment_score": 9,
  "timestamp": "2024-01-15T10:30:00Z"
}

Node 4: Check for New Feedback (core.if_condition)

This node determines whether new feedback exists before proceeding.

Configuration:

• Condition: feedback_array.length > 0
• True path: Proceeds to Node 5 (Loop Through Feedback)
• False path: Proceeds to Node 11 (No New Feedback)

This prevents unnecessary processing when no new feedback is available.

Node 5: Loop Through Feedback (core.loop)

This node iterates through each feedback item, processing one at a time.

Configuration:

• Loop source: Structured feedback array from Node 3
• Iteration variable: current_feedback
• Loop output: Processes each item through sentiment routing

Nodes 6-8: Route by Sentiment & Build Messages (core.switch + core.edit_data)

These nodes categorize feedback and format messages accordingly.

Node 6 (Route by Sentiment) - Configuration:

• Switch variable: current_feedback.sentiment_score
• Case 1 (Positive): Score ≥ 7 → Routes to Node 7
• Case 2 (Neutral): Score 4-6 → Routes to Node 8
• Case 3 (Negative): Score < 4 → Routes to Node 9

Node 7 (Build Positive Message) - Configuration:

Format: "✅ POSITIVE FEEDBACK
Customer: [customer_name]
Message: [feedback_text]
Score: [sentiment_score]/10"

Node 8 (Build Neutral Message) - Configuration:

Format: "⚪ NEUTRAL FEEDBACK
Customer: [customer_name]
Message: [feedback_text]
Score: [sentiment_score]/10"

Node 9 (Build Negative Message) - Configuration:

Format: "🔴 NEGATIVE FEEDBACK
Customer: [customer_name]
Message: [feedback_text]
Score: [sentiment_score]/10
⚠️ REQUIRES ATTENTION"

Node 10: Merge Messages (core.merge)

This node combines all formatted feedback messages into a single summary.

Configuration:

• Input sources: Nodes 7, 8, and 9 (all message types)
• Merge strategy: Concatenate with line breaks
• Output: Complete feedback summary ready for Teams

Node 11: Send to Teams Channel (microsoftteams.sendChannelMessage)

This node delivers the final summary to your Teams channel.

Configuration:

• Account: Select your connected Microsoft Teams account
• Channel: Choose your target channel (e.g., #customer-feedback)
• Message: Use the merged output from Node 10
• Message format: Adaptive Card (recommended for better formatting)

Testing Your Agent

Step 1: Execute a Test Run

1. Open your workflow in TaskAGI's editor
2. Click the "Test" or "Run Now" button in the top toolbar
3. Monitor the execution panel on the right side for real-time progress

Step 2: Verify Each Node

Node 2 (Get Nicereply Feedback):

• ✅ Check that the HTTP request returns status 200
• ✅ Verify feedback data appears in the output panel
• ✅ Confirm the response includes customer names and feedback text

Node 3 (Process Feedback Data):

• ✅ Verify structured data format matches your expected schema
• ✅ Confirm all required fields are present
• ✅ Check that sentiment scores are numerical values

Node 4 (Check for New Feedback):

• ✅ Confirm the condition evaluates correctly (true if feedback exists)
• ✅ Verify the appropriate path is taken based on feedback availability

Node 5 (Loop Through Feedback):

• ✅ Check that the loop iterates once per feedback item
• ✅ Verify each iteration processes one feedback object

Nodes 6-9 (Sentiment Routing & Message Building):

• ✅ Confirm messages are routed to correct sentiment categories
• ✅ Verify formatted messages include all required information
• ✅ Check that emoji indicators (✅, ⚪, 🔴) appear correctly

Node 10 (Merge Messages):

• ✅ Verify all messages are combined into single output
• ✅ Check formatting and readability

Node 11 (Send to Teams):

• ✅ Check your Teams channel directly—the message should appear within seconds
• ✅ Verify formatting displays correctly in Teams
• ✅ Confirm all feedback items are visible and readable

Step 3: Expected Results & Success Indicators

Successful execution shows:

• ✅ All 11 nodes complete without errors (green checkmarks)
• ✅ Feedback message appears in your Teams channel within 10 seconds
• ✅ Message includes properly categorized feedback with sentiment indicators
• ✅ Customer names and feedback text are clearly visible
• ✅ Negative feedback is highlighted for immediate attention

If issues occur:

• No Teams message: Verify Teams integration is connected and channel is selected
• Missing feedback: Check Nicereply API key and endpoint URL
• Formatting errors: Review message template syntax in Nodes 7-9
• Loop not executing: Confirm feedback array contains items in Node 3

Once testing confirms success, your workflow is ready for production scheduling!