Returnista ACTION
Resend Confirmation Email
Resends the return confirmation email to the consumer for an existing return order. Use this when a consumer did not receive their original confirmation, when an email bounced, or to re-trigger a notification after a return order is updated. To look up a return order ID, use Get Return Orders or Get Return Order first. To view the email history before resending, use Get Return Order Emails. Requires both an Account ID (from your Returnista dashboard settings) and a Return Order ID. Note: this triggers an immediate send — there is no scheduling or preview step. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Returnista account once, then configure and run Resend Confirmation Email from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "returnista-resend-confirmation-email",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
returnista: { authProvisionId: "apn_xxxxxxx" },
accountId: "Account ID",
returnOrderId: "Return Order ID",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "returnista-resend-confirmation-email",
"configured_props": {
"returnista": { "authProvisionId": "apn_xxxxxxx" },
"accountId": "Account ID",
"returnOrderId": "Return Order ID"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "returnista",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "returnista-resend-confirmation-email",
arguments: {
accountId: "Account ID",
returnOrderId: "Return Order ID",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
accountId Account ID | string | The unique identifier of your Returnista account. Find this in the Returnista dashboard under account settings. Required |
returnOrderId Return Order ID | string | The ID of the return order. Use Get Return Orders to find IDs. Required Dynamic |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- returnista-resend-confirmation-email
- Version
- 0.0.2
- App
- Returnista
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗