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.
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.
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.
What Social does for you.
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.
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.
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.
A suggested path for Social. What you can do depends on your access in the app.
Add your profiles on the Profiles page with the credentials each network gives you.
Write posts in the planner, or switch on an agent and connect a Drive folder.
Open Approvals, check each post and reply, and approve what should go out.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
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.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
socials.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.