otherapi_key

Retently

Retently is a customer experience management platform that enables businesses to collect, analyze, and act on customer feedback through surveys and integrations.

Verdict

Retently tracks customer satisfaction through NPS surveys and feedback collection. In Switchy, @mentioning Retently lets your team pull recent survey responses, tag feedback themes, update customer records, and monitor campaign performance without leaving the conversation. Customer success and product teams get the most value — they can triage detractor feedback during standups, enrich CRM data on the fly, or spot sentiment trends across cohorts. You'll need a Retently API key with read/write access; the integration doesn't send surveys directly, only reads and organizes the feedback already collected.

Common use cases

  • Triage detractor feedback during daily standups
  • Tag survey responses by product feature
  • Update customer records after support calls
  • Pull NPS trends for quarterly reviews
  • Identify at-risk accounts from recent scores

Integration

Vendor
Retently
Category
other
Auth
API_KEY
Tools
15
Composio slug
retently

Tools

  • Add Feedback Tags

    Add tags to feedback items by providing feedback ids and corresponding tags.

  • Add Feedback Topics

    Add topics to feedback items by providing feedback ids and corresponding topics.

  • Create or Update Customers

    Tool to create new customers or update existing ones by providing their details, including email, name, company, tags, and properties. use this to manage your customer base in retently.

  • Delete Customers
    destructive

    Delete customers from the workspace by providing their unique ids.

  • Get Campaigns

    Tool to retrieve a list of campaigns associated with the account. use when you need to get details about all campaigns.

  • Get Customer By ID

    Tool to retrieve detailed information about a specific customer by their unique id. use when you need to get all the details of a customer.

  • Get Customers

    Retrieve a list of customers with optional parameters for pagination, sorting, and filtering by email or date range.

  • Get Feedback

    Tool to retrieve feedback received from customers. use when you need to get a list of feedback, with optional parameters for pagination and sorting.

  • Get Feedback by ID

    Tool to retrieve detailed information about specific feedback by its unique id. use when you need to get the details of a single feedback entry.

  • Get Latest Score

    Tool to retrieve the latest nps score for the account. use when you need to get the most up-to-date nps score.

  • Get Outbox

    Retrieve the outbox of surveys that are scheduled to be sent.

  • Get Reports

    Tool to retrieve reports related to nps surveys, including scores and trends. use when you need to get campaign performance data.

  • Get Templates

    Tool to retrieve a list of survey templates available in the account. use when you need to get the available survey templates.

  • Send Transactional Survey

    Tool to send a transactional survey to customers. use when you need to send a survey to a customer after a specific event, with an optional delay.

  • Unsubscribe Customers

    Unsubscribe customers from receiving surveys by providing their email addresses.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the Integrations page. 2. Find Retently in the MCP directory and click Connect. 3. Log into your Retently account and copy your API key from Settings > API & Webhooks. 4. Paste the key into Switchy's auth dialog and click Authorize. 5. Switchy will confirm the connection and show which tools are now available. 6. Open any Space and type '@Retently get recent feedback' to test — you should see a list of survey responses from the past 30 days. 7. If the test fails, verify your API key has both read and write permissions in Retently's access settings. 8. To invoke a tool, start your message with '@Retently' followed by the action you want, like 'tag this feedback as bug report' or 'update customer email for ID 12345'.

What teammates see: by default, memories from Retently are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Recent Detractor Feedback

@Retently get the most recent feedback from detractors in the past two weeks, sorted by date descending, and show me the customer name, score, and comment for each.
Open in a Space →

Tag Feedback by Theme

@Retently add the tag 'pricing concern' to feedback IDs 4501, 4502, and 4503 so we can track this theme across responses.
Open in a Space →

Update Customer Details

@Retently update the customer with email jane@acme.com to include company name 'Acme Corp' and add the tag 'enterprise' to her profile.
Open in a Space →

Campaign Performance Summary

@Retently get all campaigns and show me the name, status, and total responses for each one.
Open in a Space →

Customer Lookup by ID

@Retently get customer details for ID 78910 and show me their name, email, NPS score, tags, and any custom properties.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Retently show me all feedback from the last 30 days with NPS scores below 7, grouped by common themes

Output

Based on Retently's feedback data, 23 responses in the last month scored below 7. The most common themes are: (1) slow response times mentioned in 9 pieces of feedback, (2) unclear pricing mentioned in 6 responses, and (3) missing integrations cited in 5 responses. Three customers specifically mentioned difficulty reaching support on weekends. This analysis combines feedback retrieval with topic detection to surface actionable patterns.

Notes

This example demonstrates how the MCP's feedback retrieval pairs with AI reasoning to identify trends. Requires API key with read access to feedback data. Note that Retently's topic detection may need manual tagging first—if topics aren't pre-configured in your account, the AI will work from raw feedback text instead.

Prompt

@Retently create a new customer record for sarah.chen@acme.com with the company name Acme Industries and tag her as enterprise-trial

Output

Customer created successfully in Retently. Sarah Chen (sarah.chen@acme.com) has been added to your workspace with company set to Acme Industries and tagged as 'enterprise-trial'. Her unique customer ID is cus_8x3k9m2p. You can now include her in NPS campaigns or track her feedback. Note that creating a customer does not automatically trigger a survey—you'll need to add her to a campaign separately.

Notes

This write operation shows how to programmatically build your customer base for NPS tracking. Requires API key with write permissions. Be aware that duplicate emails will update the existing record rather than create a new one—Retently uses email as the unique identifier, so this is safe to run repeatedly without creating duplicates.

Prompt

@Retently pull all active campaigns and tell me which one has the highest response rate in the last quarter

Output

Retently reports 4 active campaigns in your account. The 'Post-Onboarding Check-in' campaign has the highest response rate at 34% over the last 90 days (127 responses from 373 sends). For comparison: 'Quarterly NPS' is at 28%, 'Support Follow-up' at 19%, and 'Annual Review' at 12%. The Post-Onboarding campaign also has the highest average NPS of 8.2, suggesting strong early customer satisfaction.

Notes

This example combines campaign metadata retrieval with cross-campaign analysis to surface performance insights. Requires read access to campaigns and feedback. Response rate calculations depend on Retently's send/response tracking being enabled—if campaigns are triggered externally, these metrics may be incomplete. Use this to optimize survey timing and audience targeting.

Use-case deep-dives

Post-onboarding NPS follow-up

When Retently closes the loop on new customer feedback

A 6-person SaaS team sends NPS surveys 30 days after signup and wants to tag detractors for immediate outreach. The Retently MCP lets you pull feedback, filter by score, and bulk-tag responses in a single Switchy workflow—no CSV exports or Zapier delays. The Get Feedback tool surfaces recent responses, Add Feedback Tags marks urgent cases, and Get Customer By ID pulls account context for personalized replies. This works when your survey volume is under 200 responses per week; beyond that, you'll want Retently's native automations instead of manual tagging. If your team reviews feedback in a daily standup and acts on it within 24 hours, this MCP keeps the loop tight without leaving Switchy.

Customer health scoring refresh

Retently syncs NPS into your weekly account review

A 4-person customer success team reviews 50 accounts every Monday and needs current NPS scores alongside usage data. The Retently MCP's Get Customers tool pulls the full roster with properties and tags, so you can cross-reference survey sentiment against Stripe MRR or Linear support tickets in one Switchy workspace. Create or Update Customers keeps your segment tags current when you reclassify accounts mid-quarter. This scenario assumes your customer list fits in a single API call (under 1,000 records); larger books need paginated workflows or a data warehouse. If your CS team lives in Switchy for account planning and wants NPS context without tab-switching to Retently's dashboard, this integration saves 15 minutes per review.

Quarterly feedback theme analysis

When you need to aggregate NPS comments across campaigns

A 3-person product team runs NPS surveys after each feature launch and wants to spot recurring themes in open-ended feedback. The Retently MCP's Get Campaigns tool lists all surveys, Get Feedback pulls responses with text, and Add Feedback Topics lets you tag patterns as you read through them in Switchy. This beats exporting CSVs because you can annotate and categorize in real time, then share the tagged set with your team for prioritization. The workflow breaks down if you're processing more than 100 feedback items per session—manual tagging gets tedious fast. If your team does quarterly retros on customer sentiment and wants a collaborative annotation layer, this MCP turns Switchy into a lightweight qualitative research tool.

Frequently asked

What does the Retently MCP do in Switchy?

It connects your Retently customer feedback data to Switchy's AI workspace. Your team can query NPS scores, read customer feedback, tag responses, and update customer records without switching tabs. The MCP exposes 15 tools covering campaigns, customers, and feedback management — so you can ask Claude to pull sentiment trends or update customer properties inline.

Do I need admin access to connect Retently?

You need an API key from your Retently account settings. Retently doesn't use OAuth — it's a static key you paste into Switchy once. Any Retently user with API access can generate the key, but check your workspace permissions first. If your Retently plan restricts API access, you'll need an admin to enable it or upgrade.

Can the MCP send new NPS surveys to customers?

No. The MCP reads campaigns and feedback but doesn't trigger new surveys. You still schedule and send NPS campaigns from Retently's dashboard. Once responses come in, the MCP lets you tag feedback, add topics, or update customer records based on what Claude finds — but survey orchestration stays in Retently.

Why use this instead of Retently's web dashboard?

Speed and context. Instead of exporting CSVs or clicking through filters, you ask Claude to summarise detractor feedback from the last quarter or find customers tagged 'churn risk'. The MCP pulls live data, so your team gets answers in seconds without learning Retently's UI. It's faster for ad-hoc analysis; use the dashboard for campaign setup.

Who on the team should connect the Retently MCP?

Whoever owns customer success or product feedback workflows. The API key grants read and write access to all customer data and feedback, so don't share it with contractors or junior team members unless you trust them with that scope. One connection per Switchy workspace is enough — everyone inherits access through shared chats.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.