Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.serval.com/llms.txt

Use this file to discover all available pages before exploring further.

​
About Medallia Agent Connect

Medallia Agent Connect (formerly Stella Connect) is a real-time customer-feedback and coaching platform for contact center agents. Connecting Agent Connect to Serval lets workflows send feedback requests, read response data, and manage users on your tenant’s Agent Connect account without giving workflow authors direct access to the API credentials.

​
What the Medallia Agent Connect integration enables

CapabilityDescription
Automation workflowsBuild workflows that call any endpoint on your tenant’s Agent Connect API host using the Medallia API request action.
Anything defined in the Agent Connect API documentation can be accessed through Serval.

​
Prerequisites

Before connecting Medallia Agent Connect to Serval, you will need:
  1. Admin access to your Agent Connect account (required to view the Integrations page and retrieve API keys).
  2. Your Agent Connect API key and API secret for the environment you want to connect.
  3. Your tenant-scoped API gateway host (e.g. yoursubdomain.api.stellaconnect.net).
Agent Connect issues separate test and production keys. Each key corresponds to one environment, so connecting both test and production requires two Serval integration installs.

​
Retrieve your Agent Connect credentials

1

Open the Integrations page in Agent Connect

Sign in to Agent Connect and navigate to Settings → Integrations. The Integrations page lists your tenant’s test and production API keys along with a corresponding API secret for each.
2

Copy the API key and API secret

Copy the API key and API secret for the environment you want to connect (test or production).
The API secret is the HMAC signing key used to mint JWTs for every outbound request. Treat it like a password: do not paste it into source control or share it across teams. If it leaks, regenerate a new one from the Integrations page — this invalidates the previous secret immediately.
3

Identify your API gateway host

Agent Connect serves per-tenant endpoints at {subdomain}.api.stellaconnect.net. The {subdomain} segment matches the subdomain you use to sign into Agent Connect (for example, if you sign in at yoursubdomain.stellaconnect.net, the API host is yoursubdomain.api.stellaconnect.net).

​
Connect Medallia Agent Connect to Serval

1

Open the Medallia integration in Serval

Navigate to Apps → Available → Medallia Agent Connect → Connect.
2

Fill in the connection form

Paste the values you captured above:
FieldValue
API KeyFrom Agent Connect → Settings → Integrations.
API SecretFrom Agent Connect → Settings → Integrations.
API HostYour tenant-scoped API host, for example yoursubdomain.api.stellaconnect.net.
Click Save.
3

Verify the connection

Open the newly connected Medallia Agent Connect integration and run the Test Medallia Agent Connect Connection health check. A successful result confirms Serval signed a JWT with your API secret and that Agent Connect accepted the combined Authorization + x-api-key headers.

​
How authentication works

Every time a Serval workflow calls Agent Connect, the Serval proxy:
  1. Decrypts your stored API key and API secret. Neither value leaves the proxy — workflow code only sees an opaque integration ID.
  2. Signs a fresh HMAC-SHA256 JWT with your API secret. The JWT carries a valid iat (issued-at) claim and a short exp claim as defense-in-depth.
  3. Attaches both headers that Agent Connect requires to the outbound request:
    • Authorization: <JWT> (the raw JWT, with no Bearer prefix).
    • x-api-key: <API key>.
  4. Forwards the signed request to your Agent Connect API host and streams the response back to the workflow.
The token is re-signed on every request. Agent Connect rejects stale JWTs server-side, so caching a token and reusing it is not an option — the generic custom-HTTP integration, which can only inject static headers, cannot satisfy this requirement. The native integration exists to perform the per-request signing inside the proxy while keeping the API secret out of reach of workflow code.

​
Rotating credentials

  1. In Agent Connect, open Settings → Integrations and regenerate the API key or API secret for the environment in question.
  2. In Serval, open the Medallia Agent Connect integration’s configuration form.
  3. Paste the new values. Leaving a field blank preserves the previously stored value, so you must paste the new secret explicitly for it to take effect.
  4. Save.

​
Troubleshooting

Health check fails with 401 Unauthorized. - Verify the API key and API secret exactly match the ones shown on the Agent Connect Integrations page — no leading or trailing whitespace from copy-paste. - Confirm the key has not been regenerated or disabled in Agent Connect (regenerating a key invalidates the old one immediately). - Confirm you are using the same environment’s key and secret (test keys do not work against production hosts and vice versa).
Health check fails with 403 or “no permission for resource”. - The API key is valid but does not have access to the Data Return surface. Contact your Agent Connect administrator to enable the relevant API scopes for the key.
Health check fails with a DNS or connection error. - The API Host is wrong. Double-check the subdomain — it must match the one you use to sign into Agent Connect. - Paste only the host, with no https:// prefix and no path.
Workflow is hitting the wrong environment. Agent Connect test and production environments use different credentials and different API hosts. If a workflow is writing to the wrong place, confirm which environment’s keys and host are in the Serval install.

​
External resources

Need help? Contact support@serval.com for assistance with your Medallia Agent Connect integration.