Connect Esputnik to Storyblok
When something happens in Esputnik, Notis takes the next step in Storyblok. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Esputnik to Storyblok
Check Storyblok campaign content before an Esputnik send
When a campaign is ready for review, have Notis retrieve its Storyblok content and summarize missing or inconsistent details before you send through Esputnik.
Scan Storyblok for upcoming newsletter content
On a weekly schedule, retrieve upcoming Storyblok items that could support an Esputnik newsletter and receive a short shortlist for planning.
Review a localized campaign page before email promotion
When a localized campaign is queued, retrieve the specific Storyblok story in its target language and have Notis summarize it for Esputnik review.
Review recently changed campaign pages
On a recurring schedule, query Storyblok page items and receive a concise review of recent changes that may affect planned Esputnik campaigns.
Check campaign terms against Storyblok data
When an Esputnik campaign draft needs review, retrieve Storyblok datasource entries and summarize relevant approved terms for a consistent message.
Review Storyblok links before newsletter planning
On a recurring schedule, retrieve Storyblok navigation links and get a concise view of their status for Esputnik newsletter planning.
Retrieve Storyblok tags for campaign organization
When campaign planning begins, retrieve Storyblok tags and give the team a concise reference for organizing related content alongside Esputnik work.
Check Storyblok query capacity before a large scan
Before a planned content review, retrieve Storyblok's GraphQL rate limit on a schedule and receive a clear capacity note for the Esputnik campaign research run.
Pull one Storyblok page into an Esputnik brief
When a campaign brief is submitted, fetch its specific Storyblok page and prepare a compact page context summary for the Esputnik campaign owner.
Supported Triggers and Actions
Notis builds workflows that link Esputnik to Storyblok. A trigger fires from one place; an action lands in another.
Esputnik triggers
Storyblok actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Fetch Content Type Items (GraphQL)
Fetch multiple stories/content items using Storyblok's GraphQL API with filtering and pagination. Use starts_with with language code prefix (e.g., 'es/*', 'hi/*') to retrieve translated content in specific languages.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Fetch GraphQL Content Item
Tool to fetch a single story in a specific language using Storyblok GraphQL API with field-level translations. For each content type (e.g., Page), Storyblok generates a ContentTypeItem field (e.g., PageItem). Use when you need to retrieve a specific story by ID or slug with optional language translation.
Get Extension/App
Tool to retrieve a Storyblok extension/app by ID using the Management API. Use when you need to fetch details about a specific extension or app installed in Storyblok.
Get Datasource Entries
Tool to retrieve datasource entries from Storyblok via GraphQL API. Use when you need to fetch datasource data. Returns datasource entries with fields like id, name, value, and dimension_value.
Get GraphQL Rate Limit
Tool to retrieve rate limit information from Storyblok GraphQL API. Use when you need to check the maximum cost per request to calculate safe request rates (100 / maxCost = requests per second).
Get Page Item
Tool to retrieve a single page item by ID or slug from Storyblok using GraphQL. Use when you need to fetch specific page content with custom field selection. Supports both draft and published versions.
List GraphQL Content Type Items
Tool to retrieve multiple content items with pagination, filtering, and relation resolution for any Storyblok content type via GraphQL. Content types are dynamically generated as [ContentType]Items (e.g., PageItems, BlogArticleItems). Use when you need to query structured content with flexible field selection and filtering.
Query page items via GraphQL
Execute GraphQL queries to retrieve multiple page items from Storyblok with filtering options. Use when you need to fetch page content with filters like path prefix, publish date, or slug exclusions.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Connect any two apps with Notis in the middle.
Esputnik and Storyblok, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Storyblok.