Resend a sent notification
pushengage_resend_notificationResend an already-sent push notification to its original audience exactly as stored, creating a new notification and returning its ID. Use to repeat a past send without changing content.
Instructions
Sends an already-sent notification again, exactly as stored — the content cannot be changed on the way out, because the API re-reads the notification itself. Resending creates a NEW notification: the response reports its id, with the original as resent_from. Only works on a notification that has already been sent. To send a draft or a scheduled one now, use pushengage_update_notification with status="sent"; to send a changed copy, use pushengage_duplicate_notification. Subscriber-timezone sends cannot be resent, nor can a single A/B variant or a drip or triggered campaign notification. Each call dispatches a real push to the notification's original audience, so confirm with the user before calling it.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"notification_id": "<notification_id>"
},
"name": "pushengage_resend_notification"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| site_id | No | Override the currently selected site | |
| notification_id | Yes | The notification to act on. Get it from pushengage_list_notifications, or from the notification_id a send tool returned. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| resent | No | ||
| view_url | No | ||
| notification_id | No |