gbp_post — GBP Post

Field	Value
Type key	`gbp_post`
Label	GBP Post
Agent queue	`gbp-post-writer`
Plan tier	Free+ (starter, growth, professional)
Credits/unit	1
Monthly range	4–12

What it produces

A Google Business Profile post — a short promotional or informational update (typically 150–300 words) with a call-to-action suitable for publishing to a tenant’s GBP listing. Output is stored in Activity.outputPayload as structured text/JSON.

Typical structure:

Post body (150–300 characters for standard posts, up to 1,500 for offers/events)
CTA type (e.g., Learn more, Call now, Book, Order online)
Optional: event title + dates (for event posts)
Optional: offer details (for offer posts)

Pipeline sequence


gbp-post-writer ──→ Activity: done
                          │
                 [auto-approved — no review]
                          │
               Deliverable status: approved

No HITL gates. GBP posts auto-approve on agent completion.

Status machine

Status tracked on the parent Activity record only.

Activity status	Meaning
`pending`	Scheduled, waiting
`queued`	Submitted to BullMQ
`in_progress`	Worker running
`done`	Post written, outputPayload saved
`failed`	Worker error

The Deliverable moves from generating → approved automatically on done.

HITL gates

None. GBP posts are not routed to the DM approvals queue or to the client dashboard for approval. They auto-approve on completion.

Dependencies

None. The GBP post writer uses tenant strategy context (business category, location, services, tone) directly from the client context file.

DB records created

Record	Created by	Notes
`DeliverableTemplate`	deliverable-planner	Monthly quota (e.g., “8 GBP posts/month”)
`Activity`	activity-planner	One per post; `type = gbp_post`
`Deliverable`	gbp-post-writer worker	Auto-approved on completion

No dedicated content model. Post copy lives in Activity.outputPayload.

Channel requirement

No channel connection required. GBP post content is drafted and stored regardless of whether the tenant’s GBP account is connected. Publishing to GBP requires a connected account.

Key rules

GBP posts are a high-volume, low-touch deliverable — the agent writes them autonomously with no review step.
Monthly volume (4–12) is set by the deliverable planner based on the tenant’s plan tier and strategy goals.