Ways to bring your work in
byline reads connected sources in the background and makes the resulting workspace memory available to AI tools through MCP. Start with the channel where you have published the most relevant work.
Choose a route
- Connect a channel. On Sources (the Connect page), connect Instagram, a website/blog, or a public YouTube channel that is your own work.
- Forward text by email. On Sources, open Email and choose Create inbox first. Copy the workspace's address from the result or Your sources. Its form is
ingest+yourcode@inbound.byline.fyi; the code in your real address is unique. Send drafts, newsletters, or notes in the message body from the inbox owner's email address, or add another sender under Your sources → the email inbox → Allowed senders before they send. Attachments are not read. - Add a public one-off URL. Open Read a single URL on Sources, enter an article or YouTube video link that is your own work, then choose Read URL. It is queued for reading; this does not connect or watch a channel.
There is no dashboard form for pasting raw text. To bring an unpublished note in, email its text to the workspace inbox. In a connected AI tool, you can also ask byline to pin a durable brand fact, which is different from importing a draft.
Your own work
Connected sources are your own writing, video, and posts. They may inform your voice, profile, and Ideas. Source reading follows your plan's allowance, and a large channel is not guaranteed to be imported in full.
Instagram and YouTube can also bring available engagement counts. They do not import comments; comments imported earlier stay separate from the creator-voice corpus. Website and forwarded email bring text, not a comment thread or view count.
One workspace may have multiple sources within its plan's limit. Its email inbox is created once for that workspace, not separately for every team member. Studio workspaces remain separate; check which workspace is active before adding client material from a connected AI tool.