Guide
Where posts go: delivery modes
A post type has exactly one delivery mode — Buffer, SocialPilot, a remote WordPress site, or member email — chosen once on the Where it posts tab.
Where: Post types → (open the post type) → Where it posts
Buffer and SocialPilot both schedule to social networks (LinkedIn, Instagram, Facebook) — PostYard decides the exact posting moment and hands the provider a "publish now" instruction at that moment, so nothing ever sits queued a second time inside Buffer or SocialPilot itself.
A WordPress-mode post type publishes full articles — title, body, excerpt, categories, tags and a featured image — to a different WordPress site than the one PostYard itself runs on, over that site's own REST API.
Manual/member-email mode sends the approved graphic and caption to a mailing list instead of a social network, with optional per-recipient logo personalisation.
With personalisation on, PostYard puts each recipient's own company logo on their copy of the graphic — matched from the member directory by their email domain first, then their company name. Anyone it can't match to a member with a logo is LEFT OUT of that send entirely, rather than emailed a graphic with somebody else's logo or no logo at all.
Check who matches before you send: Settings → Debug shows how many members are cached and how many of them have a logo, and the reconcile screen lists every recipient it couldn't place so you can pin them to the right member by hand. A pin sticks for everyone at that email domain and beats every automatic match.
Check the list itself before you send too: Settings → Debug → Test the member-email list reads the HubSpot list for one post type and tells you how many contacts came back. It emails nobody and changes nothing — it is there because an empty or wrong list is the commonest reason a member email never arrives, and without it you only find out after the sending moment has already gone by.
If a sending moment does go by without the email going out, the post's card in Manual turns amber and says what stopped it — an empty list, a list PostYard could not read, nobody matching the member directory, or dry-run being on. Fix what it names, then use "Send all overdue now" at the top of Manual to send everything that was waiting.
Whichever route you pick, connecting real credentials is never required to save the post type — it's a checklist item on the Ready/Needs setup badge, not a gate on saving.