Righthand
← All posts

How to use a Righthand with ConvertKit

Prepare a ConvertKit or Kit broadcast preflight with lifecycle status, subscriber filters, scheduled times, and reviewed content.

Use the current Kit broadcast model

Use Righthand with ConvertKit, now presented in current documentation as Kit, to prepare a broadcast preflight. The useful output checks a particular draft or scheduled broadcast against the creator's approved brief. It should keep email sending and web publication separate when the broadcast supports both.

Kit's broadcast-list reference includes lifecycle status, send timing, targeting filters, and publishing settings. It also distinguishes broadcast records from delivery and engagement statistics. A list entry marked completed should not become a claim about every recipient's engagement.

Collect the creator's actual brief

Give the account, broadcast ID, intended subject, approved links, subscriber-filter definition, and intended send zone. For an illustrative workshop announcement, the creator supplies the registration URL, eligible segment, exclusion rules, and publication choice.

Inspect available tools through integrations. If content or targeting reads are absent, provide an approved draft export or authorize a browser review. Some listing routes omit expensive fields; missing content in a slim response is not proof that the broadcast itself is empty.

A complete example request

At 2 PM America/Los_Angeles on Tuesday, review the selected Kit workshop broadcast against the attached creator brief. Return a private preflight with broadcast ID, lifecycle status, subject, send time and zone, subscriber filter, email-template reference, approved link checks, and web-publication settings where available. Do not schedule, edit, publish, or send. Deliver to me for creator review. Reconcile the reviewed fields to the current broadcast and list anything omitted by the read route.

The example is illustrative. A link that opens is not necessarily the correct registration destination. Compare its event, date, and intended audience with the approved brief.

Define the expected preflight

An example entry might say: “Draft broadcast; correct subject; send time unset; subscriber filter differs from the creator's brief; approval required before scheduling.” The assistant should not fill the schedule with an arbitrary preferred time.

A public URL or shared publication reference can indicate a web-facing version. Confirm whether publication is intended separately from emailing subscribers. The creator may approve one route while holding the other.

Reconcile edits before sending

On a second review, match the broadcast ID and refresh content, filter, and schedule. A changed filter requires a new audience comparison, even when the subject remains the same. Do not carry forward approval of the old targeting.

Permissions, pagination, and omitted fields can limit coverage. Return a partial preflight with the missing source named. If supported scheduling or sending is authorized later, reread the resulting state and retain delivery evidence separately from the draft review.

Set authority through Righthand connection permissions. Review pricing for recurring creator preparation and keep the creator responsible for final publication and recipient decisions.