Integration

Wootric integration

Wootric (by InMoment) runs NPS, CSAT and CES customer feedback surveys. An agent can list, look up (by id, email, external id or phone), create, update and delete end users (the people surveyed, personal data) and their survey settings, list and read survey responses (all, per end user, or by promoter, passive and detractor category) and declines, record, update or delete them, read the NPS summary, segments, survey templates and email delivery statistics, send email surveys to a list of addresses or to every row of a CSV, request an end user's data export and email a bounce report. Lists return at most 30 pages of up to 50 records: narrow larger queries with the created filter. Not exposed: updating a decline (the reference gives two different routes for it). Authentication is OAuth client credentials: your Wootric application's client_id and client_secret are exchanged for a 2-hour token at the token endpoint of your environment, api.wootric.com (US), .eu or .au; an account token starting NPS-EU or NPS-AU is on .eu or .au.

Connect Wootric How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Wootric.Built from the 31 Wootric tools below, on the connection you add once.

What you can do with Wootric

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Response, 9 operations

create_responseCreate responsePOSTAgents: ask firstRecords a new survey response (score 0 to 10, optional comment) for an end user, as if they had answered the survey. This writes real survey data to your account.
delete_responseDelete responseDELETEAgents: ask firstPermanently deletes one survey response of an end user. Answers 204 with no body.
get_responseGet responseGETAgents: ask firstReturns one survey response of an end user with score, comment, tags, completion, IP address, origin URL and the end user's properties at the time.
list_end_user_detractor_responsesList end user detractor responsesGETAgents: ask firstLists one end user's responses in the detractor category, newest first by default, with comment, tags, IP address and origin URL.
list_end_user_passive_responsesList end user passive responsesGETAgents: ask firstLists one end user's responses in the passive category, newest first by default, with comment, tags, IP address and origin URL.
list_end_user_promoter_responsesList end user promoter responsesGETAgents: ask firstLists one end user's responses in the promoter category, newest first by default, with comment, tags, IP address and origin URL.
list_end_user_responsesList end user responsesGETAgents: ask firstLists the survey responses of one end user, newest first by default, with score, comment, tags, IP address and origin URL; personal data.
list_responsesList responsesGETAgents: ask firstLists survey responses across all end users, newest first by default, with score, comment, tags, IP address and origin URL; personal data. Filter by creation or update time and invalidated state.
update_responseUpdate responsePUTAgents: ask firstMarks a survey response completed or excluded from calculations (invalidated); leave a field out to keep its current value. Answers 204 with no body.

End user, 6 operations

create_end_userCreate end userPOSTAgents: ask firstCreates an end user (a person you survey) with an email address and optional external id, custom properties and dates. Returns the new end user with its id.
delete_end_userDelete end userDELETEAgents: ask firstMarks an end user for permanent deletion, by id or email; Wootric deletes it the next day from 7 AM UTC (it can take several hours). Returns the end user as it was.
get_end_userGet end userGETAgents: ask firstReturns one end user by numeric id, or by email (lookup_by_email=true) or by your external id (lookup_by_external_id=true), with properties, settings and last response; personal data.
get_end_user_by_phone_numberGet end user by phone numberGETAgents: ask firstReturns one end user by phone number, with properties, settings and last response; personal data. The number must start with +; digits alone are looked up as an end user id instead.
list_end_usersList end usersGETAgents: ask firstLists end users (the people you survey) with email, phone, external id, custom properties, survey settings and last response; personal data. Filter by email, creation or update time and opt-out status.
update_end_userUpdate end userPUTAgents: ask firstUpdates the fields you pass on one end user (email, external id, dates, custom properties); leave a field out to keep its current value. Returns the updated end user.

Decline, 5 operations

create_declineCreate declinePOSTAgents: ask firstRecords a new survey decline for an end user, as if they had declined the survey; declines count toward the decline throttle of their survey eligibility.
delete_declineDelete declineDELETEAgents: ask firstPermanently deletes one survey decline of an end user. Answers 204 with no body.
get_declineGet declineGETAgents: ask firstReturns one survey decline of an end user with survey, IP address, origin URL and the end user's properties at the time.
list_declinesList declinesGETAgents: ask firstLists survey declines (surveys an end user declined) across all end users, newest first by default, with survey, IP address and origin URL.
list_end_user_declinesList end user declinesGETAgents: ask firstLists the survey declines of one end user, newest first by default, with survey, IP address and origin URL.

Email survey, 2 operations

send_email_surveySend email surveyPOSTAgents: ask firstSends a survey email to up to 100 real recipients (Wootric creates missing end users); the eligibility check can hold a recipient back unless survey_immediately is true. Each call sends again.
send_email_survey_csvSend email survey csvPOSTAgents: ask firstSends survey emails in bulk to every row of a CSV (base64 text, up to 5000 rows; Wootric creates missing end users); the eligibility check can hold a row back unless survey_immediately is true. Each call sends again.

End user settings, 2 operations

get_end_user_settingsGet end user settingsGETAgents: ask firstReturns one end user's survey settings (whether they can be surveyed by email, mobile SDK or web SDK, and the force-survey flags).
update_end_user_settingsUpdate end user settingsPUTAgents: ask firstChanges one end user's survey settings, such as turning email surveys off or forcing a web survey; leave a field out to keep its current value. Returns the settings.

Bounce report, 1 operation

send_bounce_reportSend bounce reportPOSTAgents: ask firstGenerates a bounce report for a date range and source and emails it to the Wootric account owner. Returns nothing; each call sends another email.

Email send source, 1 operation

list_email_stats_sourcesList email stats sourcesGETAgents: ask firstLists the sources of email sends, ongoing ones (email_api, webhook_trigger) and file sends with their ids, names and dates; that id goes in send_bounce_report's source.

Email stats, 1 operation

get_email_statsGet email statsGETAgents: ask firstReturns email survey delivery statistics for a date range (send requests, emails sent, delivered, bounce, open and response rates, opt-outs) plus the raw counts.

End user export, 1 operation

request_end_user_exportRequest end user exportGETAgents: ask firstSchedules an export of one end user's data; when the file is ready, Wootric emails a link to the JSON export file. Answers 202 with an empty body, so nothing comes back here.

Nps summary, 1 operation

get_nps_summaryGet nps summaryGETAgents: ask firstReturns the NPS score with response, promoter, passive and detractor counts and response rates for a date range (the last month when none is given), in the account's time zone.

Segment, 1 operation

list_segmentsList segmentsGETAgents: ask firstLists the account's segments (end user properties such as persona or pricing_plan), each with its data type (string, date or integer) and creation date.

Survey template, 1 operation

list_survey_templatesList survey templatesGETAgents: ask firstLists the account's survey templates with their languages, and the default template id. A template id goes in survey_settings.survey_template_id of send_email_survey_csv.

Use Wootric from Claude Code, Cursor or Codex

Connect Wootric in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Wootric operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Wootric

Create your workspace
Sign up free. Nothing to install.
Connect Wootric once
Add your Wootric connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.