Skip to main content
Notra can generate content without you starting each run by hand. In Studio mode the sidebar has an Automation section with Schedules and Events, which are both rule-based automations you configure once.

​
Automation modes

Scheduled

Generate content daily, weekly or monthly from activity in a lookback window

Event-Based

Generate content when a GitHub release is published or code lands on the default branch

​
How schedules and events work

1

Pick sources

Choose the GitHub repositories the automation should read. Schedules also pull completed work from every enabled Linear integration in the workspace.
2

Pick an output format

Choose one format per automation: changelog entry, blog post, LinkedIn post, tweet or image.
3

Pick a brand identity

Use the workspace default or pin a specific brand identity, which sets the tone, audience and custom instructions.
4

Generate and review

The run analyzes the activity, writes the content and saves it as a draft, or publishes the post instead when auto-publish is on. You can review the result under Content.

​
Supported output types

Schedules and event triggers support the same five formats: Auto-publish marks changelogs and blog posts as published instead of saving them as drafts. Notra always saves social posts and images as drafts for you to review and post.
Investor updates exist as a content type for manual generation, but you cannot select them for schedules or event triggers.

​
Billing

Automated runs count against the same plan quotas as manual generation. Changelogs and blog posts use the long-form post quota, LinkedIn posts and tweets use the social post quota and images use the image generation quota. When a quota is used up, AI credits cover the run if you have them. If neither is available, the run stops and workspace owners receive an email, and adding credits or upgrading lets runs resume. For details, see Billing.

​
Choosing the right mode

Best for:
  • Immediate responses to releases
  • Changelog entries when code lands on the default branch
  • Announcing new features as they ship
Example scenarios:
  • Generate a LinkedIn post when you publish a GitHub release
  • Create a changelog entry for every push to main

​
Managing automations

You can manage each schedule or event trigger in these ways:
  • Enabled or paused. The Schedules and Events pages split automations into Active and Paused tabs, and pausing keeps the configuration.
  • Edited. You can change sources, format, brand identity, timing or auto-publish.
  • Run now. You can run schedules on demand from the row menu, while event triggers only fire from GitHub.
  • Deleted. Deleting an automation removes it permanently.
Notra rejects a second schedule or trigger with exactly the same configuration in the same workspace. Notifications. Under Settings > Notifications you can get an email when Notra creates automated content, when generation fails and when Notra skips a run because there was nothing worth writing about. Settings > Logs lists integration events (such as GitHub webhook deliveries) with their delivery status.
You can combine modes, for example by using an event trigger for release announcements and a weekly schedule for a progress digest.

​
Next steps

Set up event-based automation

Trigger content generation from GitHub releases and pushes

Configure scheduled automation

Set up recurring content generation on your schedule
Last modified on October 8, 2026