Skip to app details
Back to app library
APPNEURAL APP FAMILYMarketing & Branding

Social

Every profile, one plan, your approval

Run your social media from one place: connect every profile once, plan and publish posts on all of them, answer comments, and let AI agents prepare the work for your approval.

01 / OVERVIEW

See where it fits in your day.

A profile is connected with credentials from the network, checked with it and sealed; the same connection publishes, reads the inbox and collects numbers, and what each network's API allows is shown as it is (YouTube takes videos only; X reads need a paid plan; LinkedIn needs an approved app). A post is written once and fitted per network with its own wording where wanted, up to four pictures or one video (uploaded to R2 or by address), a link and labels, and is scheduled on a month calendar, at a time, or on a posting queue per weekday. A post leaves only from scheduled: with approvals on, an editor's post waits for an owner. The publisher runs every 5 minutes, sends each delivery once, retries after 5, 15 and 60 minutes, marks a profile whose credentials stopped working, and records an unknown outcome instead of posting twice. Every 30 minutes profiles are read: posts with likes, comments, shares and views, and new comments, mentions and replies, which are read for tone and whether they need an answer; replies go out from the inbox where the network allows it, with saved replies and AI suggestions. Analytics shows followers over time, engagement per day, per-network totals, top posts and best times, with CSV export; numbers a network does not give stay empty. Automation agents (Claude with a fixed set of tools) plan a week of on-brand posts for every profile, turn new files in APPNEURAL Drive or a Google Drive folder into posts, draft replies and email a weekly report; they have no publish or send tool, so every proposed post and drafted reply waits on Approvals for a person, each run records its steps, tokens and cost, and a monthly cap per domain stops new runs. A post can also be handed to APPNEURAL Engagement's channels and its link shortened by APPNEURAL Links. API /api/v1/profiles, /api/v1/posts, a workspace feed and an agent trigger; webhooks post.published, post.failed, approval.needed, agent.run_finished, inbox.received, inbox.replied and profile.error.

A LOOK INSIDEExample layout · sample content
This week's posts
MON9
Sample planCustomer story
TUE10
WED11
Sample planProduct tip
THU12
Sample planBehind the scenes
FRI13
Illustrative weekly layout
02 / CAPABILITIES

Built around the work you do.

What Social does for you.

01

Profiles and publishing

Connect each Page, account or channel once. Write a post once; each network gets its fitted text, pictures or video. Schedule on a calendar or a queue, with retries and a clear reason when something fails.

02

Agents with approval

Agents plan posts, turn Drive files into posts and draft replies. They can only propose: posts and replies wait in the Approvals queue, and each run shows its steps and cost against a monthly cap.

03

Inbox and analytics

Comments, mentions and replies from every profile with a reading of their tone, replies from the same place, and followers, engagement, top posts and best times.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Social. What you can do depends on your access in the app.

01

Connect

Add your profiles on the Profiles page with the credentials each network gives you.

02

Plan or automate

Write posts in the planner, or switch on an agent and connect a Drive folder.

03

Approve

Open Approvals, check each post and reply, and approve what should go out.

YOUR NEXT MOVE

Make Social part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

A profile is connected with credentials from the network, checked with it and sealed; the same connection publishes, reads the inbox and collects numbers, and what each network's API allows is shown as it is (YouTube takes videos only; X reads need a paid plan; LinkedIn needs an approved app). A post is written once and fitted per network with its own wording where wanted, up to four pictures or one video (uploaded to R2 or by address), a link and labels, and is scheduled on a month calendar, at a time, or on a posting queue per weekday. A post leaves only from scheduled: with approvals on, an editor's post waits for an owner. The publisher runs every 5 minutes, sends each delivery once, retries after 5, 15 and 60 minutes, marks a profile whose credentials stopped working, and records an unknown outcome instead of posting twice. Every 30 minutes profiles are read: posts with likes, comments, shares and views, and new comments, mentions and replies, which are read for tone and whether they need an answer; replies go out from the inbox where the network allows it, with saved replies and AI suggestions. Analytics shows followers over time, engagement per day, per-network totals, top posts and best times, with CSV export; numbers a network does not give stay empty. Automation agents (Claude with a fixed set of tools) plan a week of on-brand posts for every profile, turn new files in APPNEURAL Drive or a Google Drive folder into posts, draft replies and email a weekly report; they have no publish or send tool, so every proposed post and drafted reply waits on Approvals for a person, each run records its steps, tokens and cost, and a monthly cap per domain stops new runs. A post can also be handed to APPNEURAL Engagement's channels and its link shortened by APPNEURAL Links. API /api/v1/profiles, /api/v1/posts, a workspace feed and an agent trigger; webhooks post.published, post.failed, approval.needed, agent.run_finished, inbox.received, inbox.replied and profile.error.

Social media management for a connected domain: profiles on Facebook, Instagram, LinkedIn, X, Threads, YouTube, Bluesky, Mastodon and Telegram, a planner with a calendar, a posting queue and approvals, publishing with retries, an inbox for comments and mentions, analytics, and AI agents that propose posts and replies for a person to approve.

Engagement runs contests, polls, live sessions and broadcasts to WhatsApp, Telegram and communities; Mentions watches news and forums for the brand; Creatives designs the pictures; Links owns short links and the link-in-bio page.

Priority
P2
Portfolio
Marketing & Branding
Capability
Marketing & Branding
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:16
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

social schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

social.appneurox.com DEPLOYED

social.appneurox.com

Worker
social-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:16
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/social-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app