Connect your workflow to Faryen.

Choose the interface that fits

Use an API when your own software needs structured requests and responses. Use MCP when an AI application needs to discover and call publishing tools. Both belong to the same workspace and account model.

• API: custom dashboards, content systems, and repeatable automations.
• MCP: calendar questions, draft preparation, and agent-assisted workflows.

Start with the right workspace

Every action needs an explicit workspace. Choose the connected accounts within it before preparing destinations. Two Pages on the same network are two separate destinations, each with its own format and outcome.

A workspace timezone gives the calendar its local context. Include an explicit timezone when turning a human request such as “Friday at nine” into a scheduled time.

Prepare, review, schedule, follow

Create a draft first. Attach media and choose the format, caption, and follow-up comments for each destination. Review that plan before scheduling or publishing.

A scheduled post is a plan to publish. Check the outcome for each account afterward. A successful destination and one that needs attention can belong to the same post.

• Read the available account and format information.
• Prepare a draft with separate destination choices.
• Confirm the content, accounts, and timing.
• Schedule the reviewed plan and follow each result.

Get the connection details

These guides introduce the integration model. The public endpoint reference, credential setup, and MCP client configuration will be published with developer access.