# How to automate startup release announcements with the DunSocial CLI

> Add a reviewable DunSocial CLI step to your release workflow, using approved copy, workspace-bound secrets, JSON output and a safety delay.

- Published: 2026-08-06
- Last updated: 2026-08-06
- Author: DunSocial
- Topics: cli, how-to

---

A release workflow is good at repeating a decision. It is a poor place to invent positioning. Prepare a short public summary during review, then let CI schedule that approved text after the release succeeds.

The social step should never roll back the software release. Treat it as a visible follow-up with its own failure handling.

Search phrases: automate release announcement, startup social media CI, DunSocial CLI automation, post release notes from GitHub Actions, schedule launch post CI.

## What you will do

- Create a workspace-bound automation token.
- Schedule rather than instantly publish after a release.
- Capture structured output and failures without exposing secrets.

## Before you start

- Node.js 20 or newer and the DunSocial CLI installed with `npm install -g dunsocial`.
- A selected workspace and the DunSocial account IDs returned by `dun accounts list`.
- Browser login for a laptop, or a workspace-bound token stored in a secret manager for automation.
- A reviewed public release summary and a CI secret store.

## Step by step

### 1. Create scoped credentials

In Settings → CLI, create a token for the startup workspace. Store `DUN_TOKEN`, `DUN_WORKSPACE_ID` and the destination account ID as CI secrets.

### 2. Use approved release data

Pass a reviewed release name and public summary into the job. Do not feed commit messages or private pull-request comments directly into public copy.

### 3. Schedule with a buffer

A ten-minute delay leaves room to catch a rerun or malformed variable. Add `--json` so the workflow can parse the result.

```
npx --yes dunsocial posts schedule \
  --text "Released $RELEASE_NAME — $PUBLIC_SUMMARY" \
  --accounts "$DUN_X_ACCOUNT_ID" \
  --in 10m \
  --json
```

### 4. Log the post ID, not the token

Store the returned post ID in the job summary. Fail the social step on CLI errors, but keep it independent from the release deployment.

## Check before you finish

- `dun workspace current` shows the intended workspace before a write command.
- The command uses DunSocial account IDs rather than social @handles.
- The new item appears in DunSocial with the expected CLI source, copy and time.
- The workflow prevents duplicate announcements when a release job reruns.

## Where to go next

Document how to cancel the scheduled post by ID, and rotate the workspace token without changing any other client or workspace.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/automate-startup-release-announcements-with-the-dunsocial-cli. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login