Notion: Get Self

Retrieve your token’s bot user.

Tool ID: notion_get_self

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'notion_get_self',
  {},
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute notion_get_self --input '{}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "id": "123e4567-e89b-42d3-a456-426614174000",
    "object": "user",
    "name": "Example",
    "avatar_url": "https://example.com",
    "type": "person",
    "person": {
      "email": "jane.doe@example.com",
      "email_verified": true
    }
  }
}

Use deepline tools get notion_get_self --json for the latest machine-readable contract.

Input reference

Retrieve your token’s bot user This action does not require input fields.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.id`	`string`	Yes	—	—
`result.data.object`	`"user"`	Yes	—	The user object type name.
`result.data.name`	`string \| null`	Yes	—	The name of the user.
`result.data.avatar_url`	`string \| null`	Yes	—	The avatar URL of the user.
`result.data.type`	`"person"`	Yes	—	Indicates this user is a person.
`result.data.person`	`object`	Yes	—	Details about the person, when the `type` of the user is `person`.
`result.data.person.email`	`string`	No	—	The email of the person.
`result.data.person.email_verified`	`boolean`	No	—	Whether the person’s email is verified.
`result.data.bot`	`object`	Yes	—	Details about the bot, when the `type` of the user is `bot`.
`result.data.bot.owner`	`object`	Yes	—	Details about the owner of the bot.
`result.data.bot.owner.type`	`"user"`	Yes	—	Always `user`
`result.data.bot.owner.user`	`object`	Yes	—	Details about the owner of the bot, when the `type` of the owner is `user`. This means the bot is for a integration.
`result.data.bot.owner.user.id`	`string`	Yes	—	—
`result.data.bot.owner.user.object`	`"user"`	Yes	—	The user object type name.
`result.data.bot.owner.user.name`	`string \| null`	Yes	—	The name of the user.
`result.data.bot.owner.user.avatar_url`	`string \| null`	Yes	—	The avatar URL of the user.
`result.data.bot.owner.user.type`	`"person"`	Yes	—	The type of the user.
`result.data.bot.owner.user.person`	`object`	Yes	—	The person info of the user.
`result.data.bot.owner.workspace`	`true`	Yes	—	Details about the owner of the bot, when the `type` of the owner is `workspace`. This means the bot is for an internal integration.
`result.data.bot.workspace_id`	`string`	Yes	—	The ID of the bot’s workspace.
`result.data.bot.workspace_limits`	`object`	Yes	—	Limits and restrictions that apply to the bot’s workspace
`result.data.bot.workspace_limits.max_file_upload_size_in_bytes`	`integer`	Yes	—	The maximum allowable size of a file upload, in bytes
`result.data.bot.workspace_name`	`string \| null`	Yes	—	The name of the bot’s workspace.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation