Skip to main content
RSS and podcast integrations are feeds Automate It hosts for you. Management goes through the integrations endpoints (Admin role; these endpoints are role-gated rather than scope-gated); reading a feed is public and unauthenticated.

​
Create a feed

POST /api/workspaces/{workspaceId}/integrations/rss
{
  "name": "Engineering blog",
  "description": "Product engineering notes",
  "slug": "engineering",
  "imageUrl": "https://example.com/cover.png"
}
name is required; the slug defaults to a slugified name and must be unique per workspace (409 otherwise). The 201 response includes the two URLs that matter:
  • feedUrl — …/api/feeds/{workspaceSlug}/{feedSlug}/rss, the RSS 2.0 XML any reader or podcast app consumes
  • webViewUrl — …/feed/{workspaceSlug}/{feedSlug}, a hosted HTML view of the same feed

​
Update and delete

Feeds use the generic integration endpoints: PATCH /integrations/{integrationId} (name, description, imageUrl — empty string clears the image) and DELETE /integrations/{integrationId}. Deleting warns if automations still target the feed, and a workspace can never delete its last active integration (400).

​
Targeting a feed from tasks and automations

Feeds are addressed in outputTypes as rss:{feedSlug} (podcasts: podcast:{feedSlug}); the default slug is general. A task that outputs both an article and a social post can reference the article’s published URL in the social copy with the {articleUrl} token — see Worker mode.

​
Public feed routes

RouteReturns
GET /api/feeds/{wsSlug}/{feedSlug}/rssRSS 2.0 XML, latest 50 items, cached 5 minutes
GET /feed/{wsSlug}/{feedSlug}HTML feed page
GET /feed/{wsSlug}/{feedSlug}/{itemId}HTML article page