Supported platforms
LinkedIn (linkedin_post)Posts of around 800 characters for professional networking and thought leadership. X (
twitter_post)Posts of 280 characters or fewer, although the editor allows up to 25,000 characters if the connected account is verified (Premium or Business). Both count as social posts in billing, and social posts are unlimited on every paid plan.
Generating social posts
1
Open the create dialog
Switch the sidebar to Studio, open Content and click New post.
2
Formats
Select LinkedIn post, Tweet or both, and combine them with a changelog or blog post in the same run if you like. Pick a lookback window and toggle Pull Requests, Commits and Releases.
3
Activity
Choose repositories and Linear integrations, then deselect anything you do not want mentioned. Social posts work best when you narrow the selection to one meaningful change.
4
Identity
Choose the brand identity that should write the post, since the writer reads that identity’s reference posts first to match your voice.
outputType set to linkedin_post or twitter_post. Notra always saves these as drafts, because auto-publish is only available for changelogs and blog posts. See Scheduled Automation.
LinkedIn posts
Structure
Every LinkedIn post follows this flow:1
Hook (2 lines)
Line 1: a bold statement that earns attention without overpromising
Line 2: a rehook that challenges, twists or sharpens line 1
Line 2: a rehook that challenges, twists or sharpens line 1
2
Insight or story
What you built, discovered or learned
3
Lesson
Why it matters and what changed
4
Takeaway
A clear ending that prompts reflection or a reply
Content rules
- Around 800 characters
- One core idea, at most two supporting updates
- No hashtags and no emojis
- No PR numbers and no GitHub links
- Only line breaks and simple bullets for formatting
- Meaningful bug fixes can carry a post when they clearly improve user experience, reliability, security or performance
Example
X posts
Content rules
- 280 characters or fewer, aiming for 100 to 250
- No hashtags and no emojis
- No PR numbers and no GitHub links
- One idea per post
Tone
Notra writes posts in the tone profile of the selected brand identity: Conversational, Professional, Casual or Formal, which you configure under Studio > Brand Identity. See Brand Voice.Connecting your accounts
Publishing from Notra needs a connected account.1
Open Analytics
In Studio, open Analytics.
2
Connect
Click Connect X or Connect LinkedIn, and Notra sends you to the platform to authorize it before returning you to the dashboard.
3
Pick a LinkedIn page (optional)
If your LinkedIn login manages several pages or organizations, Notra asks which one to connect.
The connection link is valid for 10 minutes, and the user who started it must complete it.
Publishing
Open a LinkedIn or X post in the editor and click Post to LinkedIn or Post to X.1
Preview
A dialog shows the post as it will appear, with the connected account’s name and avatar, and you can make final edits here. If several accounts are connected, pick the one to publish from.
2
Publish
Click the publish button, and Notra sends the post to the platform and waits for confirmation. On success, it shows a link to the live post.
3
Save as a reference (optional)
After publishing, you can add the post as a reference to one of your brand identities so future posts learn from it.
draft to published and does not post anything to X or LinkedIn.
If no account is connected, the button opens the platform’s compose window in a new tab instead. For LinkedIn, Notra copies the post text to your clipboard so you can paste it.
Analytics
After you connect an account, Studio > Analytics shows engagement rate, followers, impressions and interactions for the selected date range, along with a leaderboard of your posts and a page per account. Notra matches posts published from Notra to their analytics automatically.Editing social posts
Use the content agent in the editor to refine a draft: Adjust the hook”Make the opening more surprising"
"Start with a specific problem statement” Change the focus
”Focus more on the performance impact"
"Highlight the technical challenge we solved” Refine the tone
”Make this more conversational"
"Simplify the language” Improve engagement
”Add a question at the end"
"Include a specific metric”
Best practices
One core idea per post
Pick the most interesting update and go deep on it. Good: Focus on one feature with clear impactPoor: List 10 different updates from your changelog
Lead with impact, not implementation
Good: “We reduced API response time by 60%“Poor: “We implemented request coalescing and caching”
Use specific numbers
Good: “Reduced build time from 8 minutes to 90 seconds”Poor: “Significantly improved build performance”
End with a question
Good: “What’s the most frustrating error message you’ve encountered?”Poor: “Check out our changelog for more details.”