Documentation

Set up ConversationArc with confidence.

Customer guides for invited workspaces, current capabilities, troubleshooting, and agent connections.

Set up ConversationArc

This guide takes a new workspace from invitation to a safe first workflow. Everything here uses the customer interface and customer-scoped access.

Before you start

You need:

  • a one-time ConversationArc workspace invitation;
  • an email address you control;
  • an Instagram professional account that is eligible for the current Meta app access;
  • owner or administrator access for provider connections; and
  • one real destination, such as an HTTPS landing page, download, event, product, or waitlist.

If your Instagram business is outside the approved app population, stop after building the paused workflow. Ask support to confirm Meta App Review availability. Do not share an Instagram password or access token.

1. Activate the workspace

  1. Open the one-time /start-workspace?token=... link.
  2. Confirm the workspace name and create your password.
  3. Sign in at https://correspond.outliyr.com.
  4. Open Account security and configure two-factor authentication.
  5. Open Legal and have the workspace owner review the exact current policy version. Only the owner can accept it.
  6. Open Billing and check its mode. Choose monthly or annual billing only when the page identifies live billing; the 14-day commercial trial begins only after live Stripe Checkout activates the subscription. If the page says Stripe test mode, stop before Checkout and ask support. Sandbox status never proves commercial activation.

Invitation links expire after 72 hours and cannot be reused. Ask the sender to rotate and resend an expired link; never request the raw token in a support ticket.

The signed-in onboarding checklist links to account security, legal acceptance, and billing before provider and workflow setup. These steps stay visible even while external Instagram authorization is waiting on Meta App Review.

2. Add teammates safely

Open Team, enter the teammate's work email, and choose the narrowest role:

  • Owner: workspace ownership, legal acceptance, team and destructive privacy controls.
  • Administrator: workflow/provider administration and destructive workflow controls.
  • Editor: routine workflow and content changes, without owner-only operations.
  • Analyst: read-only product and delivery visibility.
  • Support: redacted diagnostics access, not customer-content impersonation.

Send the generated one-time link through a secure channel. Revoking a member ends browser sessions and invalidates that member's personal agent key.

3. Create the destination first

  1. Open Resources and choose a template: course, product, download, event, podcast episode, waitlist, or custom.
  2. Give the resource a stable ID, a public slug, and an accurate title. The ID and slug are separate required fields; they can use the same value.
  3. For a direct destination, enter its canonical HTTPS URL and verify it.
  4. For an unreleased offer, keep the resource in draft or use a hosted waitlist.
  5. For recurring content, add an RSS/Atom source and review imported drafts before marking one ready.

Feed sync never silently repoints an existing workflow. A media-scoped workflow stays bound to the resource selected when its immutable version was published.

4. Connect Instagram

  1. Open Connections as an owner or administrator.
  2. Choose Connect Instagram.
  3. Complete the Meta-hosted OAuth flow for the intended professional account.
  4. Return to ConversationArc and verify the displayed external account, connection state, permission state, and configuration check.

The token is encrypted and is not shown in the UI, REST API, or MCP. If the connection reports reauthorization required, reconnect through OAuth; do not paste a token into a workflow.

An owner or administrator may instead ask an agent with a write-scoped personal

key to start the same OAuth handoff through REST or MCP. The returned

authorization URL is sensitive, single-use, and valid for 10 minutes. Open it

yourself to complete Meta consent. This is not a Turnstile or login bypass: it

does not create browser cookies or reveal an Instagram password or token.

Meta can allow the Outliyr production account while still blocking an unrelated external tenant. That is an approval boundary, not a local setup error.

5. Build a paused workflow

  1. Open Workflows and create a workflow. New workflows always start paused.
  2. Select the exact Instagram account.
  3. Select account-wide or media-specific scope and enter the keyword as a whole-word trigger.
  4. Keep the self-comment guard enabled unless you have a documented test reason.
  5. Select the resource created above.
  6. Write the private-reply template and public-reply variations.
  7. Preview the actual variables and graceful fallbacks.
  8. Save, validate, and inspect the resulting immutable version.

Supported personalization context is documented in the workflow editor. Unresolved or malformed template tokens fail closed; they must never be delivered literally.

6. Prove the safe path before activation

  1. Confirm the destination resolves to the intended page.
  2. Confirm the correct account, media scope, keyword, resource, and copy.
  3. Activate only after the UI reports the workflow ready.
  4. From a non-business test account, leave one new matching comment on an eligible current post.
  5. In Activity, locate the opaque correlation ID and confirm the private/public outcomes.
  6. Confirm the actual Instagram message and tracked destination on the receiving phone.
  7. Avoid a second matching comment from the same test fixture until the first outcome is understood.

If the provider result is unknown or ambiguous, pause the workflow and follow the recovery section in Troubleshooting. Do not blindly retry.

7. Connect an agent with MCP

  1. Open Team and create a personal agent key with the narrowest scope and expiration.
  2. Copy it once into CORRESPOND_MCP_TOKEN in your local environment.
  3. Use the configuration in examples/claude-code.mcp.json.
  4. Verify the server at https://correspond.outliyr.com/mcp and call list_workflows.
  5. Ask the agent to create changes paused and show the returned record before activation.

Never commit the key. Rotation invalidates the prior key immediately. See REST API and MCP for authentication, roles, exact-confirmation fields, and complete customer tool inventory.

8. Operational handoff

Before relying on the workflow, make sure another workspace owner knows how to:

  • pause the workflow;
  • inspect Activity and copy an opaque correlation ID;
  • reconnect the provider;
  • inspect usage and billing state;
  • export tenant data; and
  • contact support without sending secrets or raw customer content.