How to use a Righthand with NationBuilder

Quick answer

Use Righthand to prepare a NationBuilder supporter coordination list for an approved activity. Distinguish known preferences, recorded interactions, and proposed next steps.

Start with a reviewable deliverable, keeping NationBuilder as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

NationBuilder documents its API, authentication, resources, and version-specific access. See the official NationBuilder reference. Provider capabilities and Righthand's available tools are separate checks.

Use the approved organization's limited people and activity packet with list definitions, permission boundaries, and contact preferences. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: person ID, activity, tags supplied by owner, contact preference, assigned organizer, last interaction. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

A tag is not proof of intent or consent. Keep sensitive supporter context limited and preserve the organization's approved contact rules.

Illustrative first-run brief

Use the owner-provided NationBuilder snapshot or approved read-only view. Review the supplied volunteer-activity roster. Identify missing availability and unassigned follow-ups. Draft organizer questions without changing tags or contacting people. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the organizing lead to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

A person without availability remains unknown rather than scheduled. An organizer receives a proposed clarification, not an assumed commitment.

Match one person ID, preference, and activity association to the accepted roster. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Old tokens or mixed API versions can block access. Have the owner confirm the current connection and use a limited approved report if necessary.

When list membership appears broader than the agreed program, stop the audience-dependent section and ask the organizer to confirm the correct list.

FAQ

What should the reviewer verify first?

Verify person IDs, list purpose, activity dates, and permitted contact context. A shared profile or tag does not establish authorization for every campaign.

How should a repeat run be scoped?

Keep program and list identifiers, activity window, and restrictions attached to each review. Recheck changed membership and consent-related instructions before drafting another contact queue.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.