Use Buffer as a bridge, not the workflow source of truth.

• Discovers authorized Buffer channels when the configured API access permits it.
• Builds platform-specific publish payloads from approved artifacts.
• Records Buffer identifiers and scheduled state without calling a scheduled post already published.
• Reconciles later outcomes when the connector exposes sufficient status.

Buffer authorization does not automatically provide every platform field or complete post-level analytics. Pinterest board configuration and other destination-specific requirements still apply. GrowFlux does not silently replace a missing final visual with an unrelated source image.

A failed Buffer handoff remains visible on that delivery. Other destinations do not fail by default. Retrying reuses the idempotency contract so an operator or Agent can recover without creating accidental duplicates.