> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bulknotion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Use this the first time you run a bulk update — from connecting Notion through to watching the job finish.

Roughly five minutes, most of it Notion's authorisation screen.

<Steps>
  <Step title="Connect your Notion workspace">
    Open the [console](https://bulknotion.com/console) and sign in with Google.
    You will be sent to Notion to authorise BulkNotion.

    On Notion's screen, **pick the pages and databases you want BulkNotion to
    reach**. It only ever sees what you select here. Grant it the database you
    intend to update and the page holding your template.

    More detail: [Connecting Notion](/notion-connection)
  </Step>

  <Step title="Choose a database">
    Back in the console, search for the database by name. Recently edited ones
    appear first.

    If the database has more than one data source, pick the one you mean — the
    properties you can filter on come from it.
  </Step>

  <Step title="Narrow down the pages">
    By default every page in the database is targeted. Add conditions to cut that
    down — status, checkbox, select, date, text.

    The count updates as you go, so you can see exactly how many pages a
    condition catches before committing to it.

    <Tip>
      Start deliberately small. One condition that matches three pages is a
      cheap way to confirm the template does what you expect.
    </Tip>
  </Step>

  <Step title="Pick the template">
    Choose from the templates defined on that database in Notion. If the list is
    empty, the database has no templates yet — create one in Notion first.
  </Step>

  <Step title="Check the numbers, then run">
    Before starting you are shown how many pages will change and how many credits
    that costs.

    <Warning>
      Applying a template replaces each page's body, and it cannot be undone from
      BulkNotion. Read the count once more before you start.
    </Warning>
  </Step>

  <Step title="Watch it finish">
    The job reports progress as it runs. A thousand pages takes a few minutes;
    smaller runs finish in seconds. You can leave the page — the run continues,
    and **History** shows it when you come back.
  </Step>
</Steps>

## Doing this from Claude instead

The same sequence works as a conversation. Connect the BulkNotion connector, then
ask for what you want — Claude reads the database, proposes conditions, shows you
the count and cost, and waits for your yes before running anything.

<Card title="Set up the Claude connector" icon="plug" href="/mcp/overview">
  One URL, then sign in.
</Card>

## Next

<CardGroup cols={2}>
  <Card title="Credits and plans" icon="coins" href="/credits">
    What a run costs and when your balance refills.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/troubleshooting">
    Stalled jobs, failed pages, conditions matching nothing.
  </Card>
</CardGroup>