Amazon Pinpoint is retiring. Your push notifications don't have to
Amazon Pinpoint reaches end of support on 30 October 2026, and AWS Amplify's push notifications depend on it. Move device tokens, templates and campaign logic to Anythink: push built on FCM and web push, with taps that can trigger a workflow.
The same task, three ways
Send a push notification when an order ships.
The Anythink dashboard
Build it in the workflow editor. The trigger and the push step replace a Pinpoint campaign.
- ›Workflows → New Workflow: Order shipped push
- ›Trigger: an orders record is updated, status changed to shipped
- ›Add step: Send a Push Notification
- ›Title: Your order shipped
- ›Save and enable
- ✓customers get a push when an order's status becomes shipped
The Anythink CLI
The trigger and the push step, scriptable and repeatable.
$ anythink workflows create "Order shipped push" \--trigger Event --entity orders --event EntityUpdated \--filter '{"field":"status","operator":"changed_to","value":"shipped"}' \--enabled$ anythink workflows step-add 42 send-tracking-push \--action SendPushNotification \--params '{"to":"{{ $anythink.trigger.data.customer.device_token }}","title":"Your order shipped"}' \--start --enabled- ✓Workflow Order shipped push created and enabled
- ✓Step send-tracking-push added
Claude, through MCP
Describe the campaign. The assistant builds the workflow.
you › “When an order's status changes to shipped, send a push notification to the customer saying their order shipped, with the tracking link.”
- ✓Workflow: when an order's status changes to shipped
- ✓Step: send a push notification to the customer's device
- ✓Included the tracking link in the body
- ✓Enabled, and ready to try with Test Workflow
Anythink vs Pinpoint-dependent stacks
| Capability | Anythink | Amplify / Pinpoint |
|---|---|---|
| Push notifications (FCM + web push)Amplify's push notifications feature depends on Pinpoint, which reaches end of support 30 October 2026 | Built in | Add-on, extension or DIY recipe |
| iOS action categories and buttons | Built in | Not confirmed |
| Tap triggers a backend workflow | Built in | Not confirmed |
| Bulk fan-out via a queue | Built in | Not confirmed |
● Built in◐ Add-on, extension or DIY recipe– Not available? Not confirmed
Amplify/Pinpoint column reflects published AWS documentation on the Pinpoint migration requirement, not a feature-by-feature audit of every Amplify configuration.
What moves, and what doesn't
Device tokens, templates and campaign logic all have a direct home in Anythink. Here is what each one becomes.
Device tokens, no separate service
Devices register against your project's own push endpoint, not a third service you have to wire up. FCM and web push (VAPID) are both supported, with per-project credentials and per-device records you can list or revoke.
What a migrated send looks like
Real requests against the push API
POST https://api.my.anythink.cloud/org/{org_id}/push/devices { "provider": "fcm", "token": "<device-token>", "platform": "android" }
Moving a Pinpoint setup
Re-register your device tokens
Export the endpoints from Pinpoint and re-register each device against your Anythink project's push endpoint, tagged with its provider (FCM or web push). This is a one-time batch job, not a new integration to maintain.
Turn campaign logic into workflow triggers
A scheduled Pinpoint campaign becomes a Timed trigger. A behavioural campaign (send on an event) becomes an Event trigger with a filter, like status changed_to "shipped". Both are configured in the dashboard or with the CLI, not in campaign-definition JSON.
Rebuild message templates as push templates
Recreate your Pinpoint message templates as Anythink push templates. If a campaign used custom data per recipient, the template variable syntax pulls fields straight from the triggering record or an earlier workflow step.
Wire up action buttons, if you used them
iOS action categories carry the button order and labels to the device. Point each action at a workflow trigger instead of a Pinpoint event handler, and the tap does the same job it always did — just verified and triggered on your own backend.
Next
Push with action buttons
Add buttons to a notification and point each tap at a workflow on your own backend.
Push notifications →