Generic API automation
Generic API automation is an automation task type that calls an HTTP API you specify on a schedule and turns the response into a post, instead of relying on Autogram's own AI generation or a curated RSS/news feed. You configure the method, URL, headers, and body once as a saved API template, and every scheduled run replays that exact request. A template can be personal, built for your own account, or a system preset Autogram ships for a common case; either way the automation task just points at a template and runs it on the schedule you set. Supported methods are GET, POST, PUT, PATCH, and DELETE, with none, Bearer, API-key, or Basic authentication, so the request can reach an endpoint that requires a credential without that credential living in the post text.
A template is the reusable half, the task is the schedule
The API template holds everything about the request itself — method, URL, headers, body — and stays the same across runs. The automation task is the separate half that decides when to call it and what to do with the response; the same relationship an AI instruction has to the automation that reuses it, just for an HTTP call instead of a prompt.
System presets versus your own templates
A system preset is a template Autogram publishes for you to reuse as-is or copy and adjust; a personal template is one you built yourself, scoped to your account. Both run through the same task type — the distinction is only about who owns the definition, not about what the automation is allowed to do with it.
Authentication stays on the template
Each template declares its own authentication — none, Bearer token, API key, or Basic auth — so a request to a protected endpoint carries its credential as part of the saved template rather than pasted into an instruction or a post body where it could leak into generated content.
Why it exists alongside RSS and the news feed
RSS automation and the curated news feed both turn content you do not own into posts, from a feed or a shared source. Generic API automation is for the opposite case: pulling structured data from an endpoint you do own or control — your own backend, a stats API, an internal system — into a post, which neither an RSS reader nor a curated feed can reach.
Related terms
Related features
Put these concepts to work
Automate your Telegram publishing with AI content, quality scoring, and smart scheduling.