AfieldConnect the account that will do the work
Open Integrations to choose the mailbox, site or other destination available to your workspace. Afield can prepare content before that connection is ready, then use the connected account when you approve the external action.
Draft, publish and send are separate choices
| Work | Review before execution | Inspect afterwards |
|---|---|---|
| Sender, recipient, subject and final body | The send result and the message in the connected mailbox where available. | |
| Website article | Exact site, title, body, images and draft/publish choice | The destination draft or public URL. |
| Social content | Supported account, format, text, media and links | The provider result or post URL. |
For example, “Save this article as a draft on my connected WordPress site” specifies a different action from “Publish this article.” Afield keeps the publication step distinct from the finished writing.
Carry one article into a small campaign
An approved supplier-drawing guide can become a website article, an email offering the example and a short post about one drawing mistake. Request each version from the same material, then choose the destination for each.
You do not need to reconstruct the source research for every channel. You do need to review the actual version that will leave the workspace, because an email recipient and a public article reader need different context.
Use the receipt to continue
Task history links available saved deliverables and execution records back to the conversation. A saved draft can be reopened; a returned publication URL can be visited. If a send or publish request loses its connection, inspect the destination before repeating it.
Availability depends on the connection and its permissions. The integration directory describes setup; the channel-action guide covers final review.
Choose the interaction the platform supports
Publishing a post and replying to a person use different platform permissions. See the social-action support table and complete reply example before preparing an interaction. In particular, Afield’s connected LinkedIn API does not expose direct messages or connection requests.