Your writing, connected.

Start with a project

1. Complete the connection steps above, then enable the Dialogue connector in the assistant conversation you want to use.
2. Ask it to find your project by name and read it. If names repeat, identify the exact project before asking for edits.
3. Describe the scene, outline section, card, or character you want to work on. The assistant looks up the saved IDs for you.
4. Ask it to save the change. A successful write returns saved: true; the project then updates in Dialogue.

For a review first, ask the assistant to show a proposed revision in the conversation and wait for your instruction to save. You can also use the connector only to read, summarize, or discuss a project.

Create projects and outline sections in Dialogue first. The connector currently edits existing projects; it has no project-creation or section-creation tool.

Example prompts

Replace the example project, scene, and character names with your own. Say “use Dialogue” so your assistant uses the project tools.

Explore without editing

Use Dialogue to find my project “Northbound.” Read its cast and outline, then summarize the story and list its scenes. Do not save any changes.

Continue a scene

Use Dialogue to read the train-platform scene in “Northbound.” Append a short action beat and two lines of dialogue between its existing characters. Keep the tone restrained and save the additions.

Revise existing writing

Use Dialogue to read the train-platform scene in “Northbound.” Show me a tighter version of Mara’s last line. Wait for me to approve the wording before saving it.

Develop an outline

Use Dialogue to read the “Northbound” outline. Add three new beat cards to its existing “Act II” section, building toward the midpoint. Keep the existing cards and attachments.

Develop the cast

Use Dialogue to read “Northbound.” Analyze each character’s role and objective, then update those two fields for the existing cast. Preserve the screenplay and outline.

Add a character

Use Dialogue to add a character named Ellis to “Northbound,” with the role “Station attendant” and the objective “Keep the platform clear before the last train.”

Attach an image you already have

Use Dialogue to find the “Last train” outline card in “Northbound.” Set its image to the HTTP or HTTPS image URL I provide. Keep its title and description.

All six tools

Your assistant supplies these arguments. You can normally describe your task in words; this reference is useful when directing a precise workflow or building another MCP client.

The first five tools read data. apply_project_changes is the only tool that changes a project.

All seven edit operations

A single changes batch contains 1–30 operations on one project. Expand an operation to see every supported field. Fields not listed in its schema are rejected.

Read, then write

Use the exact version from the latest project or scene read as expectedVersion. Give each new write a fresh UUID changeId. If another session saves first, read the project again and reapply your intended change to the current content.

Retry an uncertain write with the same changeId and identical arguments. A successful identical retry returns alreadyApplied: true, preventing duplicate additions. Different arguments need a new change ID.

{
  "projectId": "your-project-id",
  "expectedVersion": "the-version-returned-by-get_project",
  "changeId": "123e4567-e89b-42d3-a456-426614174000",
  "changes": [
    {
      "operation": "append_blocks",
      "sceneId": "scene:your-heading-block-id",
      "blocks": [
        {
          "type": "action",
          "text": "The last train disappears into the fog.",
          "characterId": null
        }
      ]
    }
  ]
}

Use AI mode from Dialogue

1. In the mobile or web writer, turn on AI mode and submit your instruction. Outline actions can also prepare assistant requests.
2. Dialogue saves outstanding project changes, creates a pending request, and shows a handoff with a prompt to copy.
3. Paste that prompt into your connected assistant. It reads get_request, reads the current project, and saves supported edits with the matching requestId.
4. A successful save marks the request completed. Dialogue shows that status and receives the updated project through Firebase.

You can also ask: “Use Dialogue to list my pending requests. Show me the instructions, then complete the one I choose.” Requests run when you ask the assistant to act; the queue does not run automatically.

Request statuses are pending, completed, and cancelled. Cancel a pending request in its Dialogue handoff. A cancelled or completed request cannot be completed again with a different write.

The model runs in Claude or ChatGPT. This connector does not embed a personal assistant subscription inside Dialogue, generate images itself, or automatically run a prompt when you open an assistant link.

Choose access and manage connections

projects.read

Required for project and request reads. A read-only connection can summarize, review, and propose changes in the assistant conversation.

projects.write

Optional editing access, requested alongside read access. Enables apply_project_changes.

Consent grants account-wide access to projects you own, rather than access to one selected project. Projects shared with you by someone else are not exposed as your source projects. Selecting an AI request supplies its task context; it does not change the connection’s account-wide scopes.

Use Dialogue Settings → Connected assistants to see actual connections and revoke access. On mobile, this is under Settings → Writing → Connected assistants. Revocation blocks subsequent project access immediately. Reconnect and approve the desired scopes when you want to restore access.

Current boundaries

These tools support the edits listed above. They do not create or delete projects, delete or reorder blocks/cards, create or reorder outline sections, rename existing characters, edit sharing permissions, manage billing or keys, select models, upload files, or export documents. Existing image/video attachments are preserved by text edits; setting an image explicitly replaces that card’s media.

Before-images are recorded server-side for saved edits, but the connector has no undo or restore tool. Use Dialogue’s own controls for actions outside the tool set.

Troubleshooting

The assistant replies, but nothing changes

Make sure Dialogue is enabled in that conversation and ask it to use the Dialogue tools to save. A proposed draft in the conversation is not a saved edit. For an AI-mode request, the save must include its requestId to mark it completed.

Sign in / reconnect / invalid token

Reconnect from the assistant and sign in to the intended Dialogue account. Expired access tokens can normally be refreshed by the client. Revoked connections or rejected refresh grants require a new connection.

Editing access is missing

The grant may be read-only. Reconnect with projects.read projects.write; the consent page shows the requested access.

Project or request not found

Check the account and use IDs returned by the tools. Only owned projects and your own requests are accessible. Requests are separate from project IDs.

The project changed / conflict

Read the current project again. Reconcile the intended change with the new content and use the new version and a new change ID. The rejected batch has not partially saved.

Wrong scene, section, card, or request target

Read the request and current project, then use their exact IDs. Scene names are not unique identifiers. A request-completion write must match its kind and target.

Invalid tool arguments

Use the operation’s listed fields, valid enum values, and current IDs. Dialogue blocks require an existing character ID; other block types require null. Respect field and batch limits.

A project is unavailable or has unsupported changes

Open it in Dialogue and resolve the format or external-edit issue before retrying. The connector rejects records it cannot safely interpret.

Request cancelled or already completed

Create a new request for new work. An identical retry of the original successful write can still return its existing receipt.

Too many requests

Pause and retry after the hourly limit renews. Repeated retries count toward usage.

Technical reference

For MCP client developers and precise tool-directed workflows.

Back to connection steps