Wow! Build your WhatsApp integration. Start free. Register Now
RSS to Channel · WhatsApp API use case

Post a WordPress RSS item to a WhatsApp Channel

Channel subscribers see each new site article as a link-preview announcement. When your backend detects a new WordPress RSS item, it can resolve the Channel once, store that id, and post the article title with its URL through Whapi.Cloud. This use case shows integrators how to implement that flow through the WhatsApp API.

Triggered by a new item on a watched RSS feed Link preview posts to a WhatsApp Channel
Laptop showing a WordPress RSS feed beside a phone with a WhatsApp Channel link-preview post for the new article.
Decorartive bubble
Use case

When to use this flow

Your backend already watches the RSS feed

Use this flow when your own backend polls or receives a new WordPress (or similar CMS) RSS item and that item is the source of truth for what should appear on the Channel.

The destination is a WhatsApp Channel

Use this flow when subscribers should see the announcement in a WhatsApp Channel, not in a private chat list and not as a group invite.

The post should carry the article URL as a link preview

Use this flow when the Channel update must include the site article link as a link-preview announcement, not a plain text paste without that URL.

WhatsApp Channel on a phone showing a link-preview post with an article title and a link to the WordPress story.
Customer experience

Subscribers get the article link in the Channel

Before automation, the article is already live on the site and in RSS, but Channel subscribers wait while someone opens WhatsApp and pastes the link by hand.

After the flow runs, Channel subscribers see a link-preview announcement with the article title and a link back to the site post. Integrators build this result with the WhatsApp API.

Workflow

From an RSS item to a Channel link preview

1

New RSS feed item

Your backend detects a new item on the watched WordPress RSS feed and reads the article URL, title, and optional image. Whapi.Cloud does not host the feed poll.

2

Resolve the Channel id once

GET /newsletters

getNewsletters returns your Channel list so you can pick the target Channel JID, store it on your backend, and skip this call on every later RSS item unless the Channel changes.

3

Post the article link preview

POST /messages/link_preview

sendMessageLinkPreview posts the announcement to the stored Channel JID with the article URL in the body and the title for the preview card.

Need delivery tracking? A successful send response is not proof subscribers already see the Channel post. Track later acks on delivery webhooks. Learn about delivery status →

Prerequisites

Before you run the flow

Connect the WhatsApp number that administers the Channel and authenticates every request with that number's API token. RSS watching and WordPress feed parsing stay on your backend.

Optional — go deeper for this flow

API implementation

The calls that post the article

Your backend already found the new RSS item and knows which Channel should receive it. These calls resolve that Channel id when you need it, then deliver the article as a link-preview announcement.

Get your API token for free after you register on whapi.cloud, and use that token in the code instead of Your_Token from the examples.

Resolve the Channel id once

List your Channels so you can store the target Channel JID once before RSS items start posting.

Post the article link preview

Send the article title and URL to the stored Channel JID as a link-preview announcement for each new RSS item.

Delivery status

When the Channel post leaves pending

A successful send response does not mean Channel subscribers already have the post. The first status visible before a webhook is pending. Later status changes arrive only on statuses.post and statuses.put. If the status stays pending and does not move to sent, delivered, or a later ack, the message was not delivered—check the payload and the account's permission to send that type.

  • Treat a stuck pending as not delivered, not as a clock or a queue waiting on a webhook.

  • Subscribe to statuses.post and statuses.put when you need sent or delivered confirmation for the Channel post.

  • Do not mark the RSS item synced while the WhatsApp status stays pending.

What to read on delivery and webhooks

Contact our support if something went wrong
When things break

Handle failures at each step

If the RSS item is new but getNewsletters cannot match a Channel, the wrong JID was stored, sendMessageLinkPreview is rejected, or the post never leaves pending, retry or alert and do not mark the feed item as synced to the Channel.

The feed updated, but the Channel stayed quiet?

Keep RSS item state separate from Channel delivery. Confirm the stored Channel JID, retry sendMessageLinkPreview with the article URL in the body, or alert ops—do not mark the item synced while subscribers still have no post. If the Channel post still fails after a retry, contact Whapi support with the Channel id and the failed request id.

Contact our support if something went wrong

Troubleshoot by API step

FAQ

RSS items and WhatsApp Channel posts

Supported WhatsApp Features

Everything you need to build WhatsApp automation

Whapi.Cloud gives you access to a complete set of WhatsApp features — messaging, media, groups, channels, webhooks and more. Build bots, automations and integrations without feature limitations.

Chosen by developers

Trusted by 3,300+ developers and SaaS teams

Developers worldwide rely on Whapi.Cloud to build automations, bots, CRM integrations, bulk messaging tools and advanced WhatsApp workflows. Our infrastructure processes millions of API requests with high stability — and grows every month.

Icon of feature

5,5K+

active API channels

Icon of feature

21M+

API requests processed monthly

“Everything is simple, intuitive and easy to navigate. The docs are clear, and all the info I need is right on the screen. Great job.”

roberto k. / Web Developer

“We connected WhatsApp to our workflows using n8n in just a few minutes. No code, no complications- everything worked on the first try.”

Martin p. / Developer

“Whapi.Cloud became a key part of our customer communication. We automated product updates, order notifications and support messages without needing Meta templates or approvals”

Oscar T. / CTO

Decorative bubble