All guides
User

Web Push Rss

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /portal/web-push/rss on your site.

Steps

Create or update: Save changes / Add feed

  1. Open /portal/web-push/rss/create on your application domain, using the workspace account for this task.
  2. Find the form containing Feed name, RSS or Atom URL, Web Push site. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Use the button shown for the current state: Save changes, Add feed. Creation and editing can show different labels; submit the form once.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Feed nameRequired. Enter the feed name for this task, using the help or example shown by the form. The form’s example is Product updates. Replace it with your own value. Maximum 160 characters.
RSS or Atom URLRequired. Enter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. The form’s example is https://example.com/feed.xml. Replace it with your own value. Maximum 2048 characters.
Web Push siteRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving.
AudienceOptional unless the current form requests it. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving.
Subscriber topicRequired. Enter the subscriber topic for this task, using the help or example shown by the form. The form’s example is updates. Replace it with your own value. Maximum 40 characters.
Delivery modeRequired. Choose Send automatically, Create draft for review.
Maximum items per syncRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Between 1 and 10 new items. Minimum 1. Maximum 10.
Check this feed automaticallyEnter the check this feed automatically for this task, using the help or example shown by the form. Active feeds are checked every five minutes. Pause this when you want to keep the configuration without processing new items.
Notification titleRequired. Enter the notification title for this task, using the help or example shown by the form. Maximum 120 characters.
Notification messageOptional unless the current form requests it. Enter the notification message for this task, using the help or example shown by the form. Keep the message concise so the important part remains visible in browser notifications. Maximum 5000 characters.
Notification iconEnter the notification icon for this task, using the help or example shown by the form.
Large imageEnter the large image for this task, using the help or example shown by the form.
Click URL templateRequired. Enter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Use :token to send subscribers to the original RSS item. Maximum 2048 characters.

Use Sync

  1. Open /portal/web-push/rss on your application domain, using the workspace account for this task.
  2. Select the intended record or item first and review its displayed values. There is no separate input form described for this control.
  3. Select Sync. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

Source-only route information
MethodSource-default route
GET/portal/web-push/rss