Approve GEO Content Brief
Irreversibly approve a draft or failed brief and queue the paid Notra writer. This claims the brief and books writer work.
Create and manage content, AI agents, feedback workflows, and generative engine optimization data with Notra.
Irreversibly approve a draft or failed brief and queue the paid Notra writer. This claims the brief and books writer work.
Destructively cancel every post destination that has not started and clear failed destinations. A destination already publishing cannot be interrupted; it finishes and is not retried, and in_progress reports this case.
Starts a durable paid AI agent session with an initial user message and returns its session ID. Read subsequent output from the session event stream. This can consume credits and produce unbounded streamed model output; do not retry blindly after an ambiguous failure.
Create a paid Notra chat, persist the first message, and wait for the full assistant stream. The response is newline-delimited stream text rather than parsed message parts and may run for an unbounded model/tool duration. Limited with chat messages to 30 requests per minute per organization; retrying creates another chat and may repeat tool side effects.
Creates a persistent GitHub event automation that generates the selected content type for matching releases or pushes and can publish the result automatically. This is a paid operation.
Create a persistent GEO project linked to a brand identity. Requires an active paid plan or positive AI credit balance and a GEO plan.
Persist a custom prompt for future GEO scans. Requires paid access and an active GEO plan.
Irreversibly queue a paid GEO scan that records checks against configured answer engines. The scan record is created before hand-off; poll the returned status URL. Requires sufficient plan or AI credits, rejects concurrent scans with 409, and is limited to 4 requests per hour per organization.
Persist a one-to-five-turn GEO prompt sequence for tracked runs. Requires paid GEO access.
Connect a GitHub repository to Notra, enabling changelog generation and creating a webhook secret. This paid operation stores a supplied personal access token for private repositories; never pass a token unless required. Limited to 20 requests per minute per API key.
Create a draft or published Notra post directly from supplied content without invoking AI generation.
Creates a recurring schedule that generates one content type from the selected GitHub integrations. Times are in UTC. A schedule with the same source, targets, output, and lookback settings as an existing one is rejected with 409. This paid operation creates a persistent recurring automation that may generate and auto-publish content on future runs; review enabled and auto_publish before calling.
Creates a custom skill. Names must be unique within the organization. This paid operation creates a persistent agent skill.
Create a paid outbound webhook subscription that causes persistent external deliveries. The signing secret is returned only once and must be stored securely.
Permanently delete a non-default brand identity and disable every schedule or event trigger that references it. The default identity cannot be deleted.
Delete an event trigger. Permanently delete an event trigger and stop future matching events from running it.
Permanently stop tracking a competitor and return the remaining competitor list.
Permanently delete a GEO project and cascade-delete its settings, prompts, sequences, competitors, scans, checks, and reports, while cancelling pending scans. Feedback is detached, not deleted. The last project or a project with hosted Sites cannot be deleted.
Permanently stop tracking a GEO prompt. This destructive change removes it from future scans and requires an active GEO plan.
Permanently delete a tracked GEO prompt sequence so it can no longer be run.
Permanently delete a Notra GitHub or Linear integration and disable every schedule or event trigger that targets it.
Permanently delete one Notra post by ID. Use only when the post is no longer needed; this operation cannot be undone.
Deletes the schedule and stops future runs. Posts generated by earlier runs are kept. Permanently delete a schedule and stop future runs; posts from previous runs remain.
Deletes a custom skill. System skills cannot be deleted. Permanently delete an agent skill.
Permanently remove a Notra webhook subscription and cancel all deliveries that have not yet been sent.
Create a brand identity immediately and queue a paid, irreversible website-analysis job that fills its company, tone, and audience fields. Poll NOTRA_GET_BRAND_IDENTITY_GENERATION; limited to 5 requests per minute per API key.
Queue a paid, irreversible AI post-generation job. The call consumes plan capacity or credits even if later generation fails. Poll NOTRA_GET_POST_GENERATION until terminal; limited to 10 requests per minute per API key.
Get one Notra brand identity by ID. A missing identity is represented by a successful response with brand_identity set to null.
Get a brand identity analysis job. Poll until status is completed or failed, then fetch job.brand_identity_id with NOTRA_GET_BRAND_IDENTITY.
Get one Notra chat and its complete message history by chat ID.
Find the Notra chat linked to a Discord or Slack channel ID.
Returns one GitHub event trigger with its event filters, monitored repositories, generated content type, and publishing settings.
Returns one feedback entry with its classification, triage status, submission context, and timestamps.
Get the latest stored agent-readiness report, any newer run state, score history, and comparison for a GEO project's website without starting a scan.
Read paid-plan competitor share-of-voice metrics without starting a scan.
Read one competitor's paid-plan mention history without starting a scan.
Read one stored paid-plan GEO content brief without approving or starting writer work.
Read paid-plan traffic installation snippets and endpoints. This does not issue or rotate credentials, but deploying the returned setup changes external traffic collection.
Read paid-plan GEO visibility by language without starting a scan.
Get one GEO project. All GEO endpoints require an active GEO plan.
Read stored paid-plan checks for a tracked prompt without starting a scan.
Read one stored paid-plan prompt result without starting a scan.
Read stored paid-plan prompt answers and grounding data without starting or billing a scan.
Get one GEO scan's status, progress and mentions by engine, including safe failure metadata. Legacy scans may have null planned totals. Requires an active GEO plan.
Read current and previous paid-plan GEO sentiment metrics without starting billed analysis.
Read cached paid-plan thematic sentiment analysis. This never starts or bills a model run.
Get the complete GEO configuration and current scan state for a project. Requires an active GEO plan.
Read the paid-plan events in one AI traffic journey without changing tracking setup.
Read a bounded set of recent paid-plan AI traffic events without changing tracking setup.
Get AI crawler, citation, referral, and conversion traffic totals, source breakdowns, and daily points for a GEO project.
Get mention rates, checks, citations, visibility, and average positions by answer engine for a GEO project and date window.
Read paid-plan daily GEO visibility metrics. This does not start a scan or bill an analysis job.
Get one Notra post by ID, including its rendered content, markdown source, metadata, and publication status. A missing post is returned as post=null.
Get a post generation job and event log. Poll until status is completed, failed, or skipped; when completed, fetch job.post_id with NOTRA_GET_POST.
Get a post's current publishing schedule and the state of every destination, or null when no schedule exists.
Check whether Notra's public API is reachable and discover its authentication metadata without a connected credential.
Returns a skill by name, including its full instructions and whether it is built into Notra.
Get one Notra webhook delivery, including its serialized payload and complete attempt history.
Return the workspace and authentication context bound to the connected Notra credential, optionally including pending workspace invitations.
Bulk create or update a project's persistent competitor list from up to 2,000 rows or CSV. Existing names are updated rather than duplicated; send the whole list in one request. Paid GEO operation limited to 10 requests per 10 minutes per organization.
Bulk-persist up to 500 tracked prompts from rows or CSV. Existing prompts are skipped rather than duplicated. Requires paid GEO access and is limited to 10 requests per 10 minutes per organization.
Returns the current tracking token together with the install snippets. Pass `projectId` for a project-specific token; without it, the legacy token only accepts the organization's oldest project's hosts. Issuing does not invalidate previously issued tokens; use rotation for that. Issue a sensitive GEO ingest bearer token. Store the returned token securely and never log or expose it.
Returns recent agent sessions and their linked chat IDs, origin surfaces, statuses, and timestamps. Results can contain sensitive conversation metadata.
List the workspace's brand identities, with the default first, for selecting brand context in content and GEO workflows.
List the workspace's Notra chat sessions without loading message histories.
Returns the organization's GitHub event triggers, optionally filtered to triggers monitoring any of the supplied repository IDs.
List workspace feedback with optional triage-status, kind, and project filters.
Compare the two latest stored paid-plan GEO scans without starting a new scan.
List competitors tracked for a GEO project. Requires an active GEO plan.
List stored paid-plan GEO briefs. This read does not plan, approve, or bill work.
Read paid-plan content opportunities and linked briefs. This does not plan, approve, or bill content work.
List the connected workspace's paid GEO projects and their brand associations.
Return one bounded page of stored paid-plan prompt result summaries; no scan is started.
List custom and automatically derived prompts tracked for a GEO project. Requires an active GEO plan.
List paginated GEO scans with planned, completed, mentioned, and failed check totals by engine plus safe failure metadata. Requires an active GEO plan.
Return one bounded page of stored paid-plan sentiment evidence without starting analysis.
List tracked multi-turn GEO prompt sequences. Requires an active GEO plan.
Return one bounded page of paid-plan cited and tracked GEO sources without starting a scan.
List a bounded set of paid-plan AI traffic journeys without changing tracking setup.
List a bounded paid-plan ranking of pages visited by AI traffic without changing tracking setup.
List enabled GitHub and Linear integrations and their IDs for use as Notra content-generation sources. The Slack list is always empty.
List Notra post authors and their IDs for assigning authors to blog posts and changelogs.
List the connected workspace's posts, with filters for publication status, content type, and brand identity. Notra returns published posts only unless statuses includes both draft and published.
Returns the organization's cron schedules, newest first. repositoryMap maps each targeted GitHub integration ID to an owner/repo label.
Returns the organization's skills sorted by name, including built-in system skills (isSystem: true). Skill content is omitted; use GET /v1/skills/{name} to read it.
List Notra webhook delivery history at a specific offset, optionally filtered by delivery status. Increase offset to continue when has_more is true.
List Notra outbound webhook subscriptions without exposing their signing secrets.
Plan and save a GEO content brief. This paid operation books AI credits; autoApprove also starts the billed writer. A 409 after four minutes may still finish, so do not retry; list briefs instead.
Persist a message or tool-approval decisions in an existing paid Notra chat and wait for the full assistant stream. Earlier history is included automatically. The response is newline-delimited stream text and may run for an unbounded model/tool duration. Tool approvals can trigger external mutations; retrying can duplicate them. Limited with chat creation to 30 requests per minute per organization.
Replace the project's GEO settings and re-arm its recurring scan. Unknown engines or languages are rejected; hidden engine selections are retained, the prompt language remains tracked, and ZDR is disabled without its add-on. This persistent scheduling change requires paid access and a GEO plan.
Queue a paid redelivery of a failed webhook while retaining its prior attempt history. This sends the payload to the external endpoint again and can duplicate downstream effects.
Invalidates every tracking token previously issued for this organization and returns a fresh one. Deployments still sending the old token stop being accepted immediately. Irreversibly rotate the sensitive GEO ingest bearer token, immediately invalidating the previous token. Store the replacement securely and never log or expose it.
Irreversibly execute every turn of a tracked sequence against every available answer engine and record checks, consuming paid Notra model capacity. The synchronous call may take minutes and is limited to 10 runs per 10 minutes per organization. A 409 after four minutes means work continues; do not retry and instead read project GEO checks.
Schedule a paid future publication that marks the saved post published in Notra and can create and merge a GitHub pull request or post to X or LinkedIn. Replaces any schedule that has not started; later post edits are included. Publishing occurs within about one minute and transient failures retry automatically.
Sends the next turn of an agent session. The server binds the session's stored continuation token, so the client-provided one is ignored. Answer input.requested events (tool approvals, questions) from the event stream via inputResponses. Send a paid message to an AI agent session. This can consume credits and produce unbounded streamed model output; do not retry blindly after an ambiguous failure.
Queue a paid readiness scan of the project's linked website. This starts external scanning work; an identical in-flight scan may be reused.
Fetch and parse the durable NDJSON event response for an agent session after Notra closes the response, including input.requested events for tool approvals. This call does not deliver events incrementally and returned events can contain sensitive conversation content.
Record feedback for the organization that owns the credential. Requires an API key with the feedback.write scope. Agents and MCP servers should post to the organization's feedback URL instead. Submit persistent workspace feedback. This paid write has no delete endpoint.
Record feedback from an AI agent or integration by posting to the organization's feedback URL, as shown on the Feedback page in the dashboard. No credentials are required. Limited per source IP and per organization. Submit persistent feedback without authentication. This paid write has no delete endpoint and is rate-limited by source IP and organization.
Use Notra's paid discovery operation to suggest competitors for a domain. Results are cached per organization and domain; requests are limited to 10 per 10 minutes per organization.
Update selected fields of a Notra brand identity. This paid mutation can also change the organization's default identity by setting is_default to true.
Replaces an existing GitHub event trigger's filters, monitored repositories, generated content type, and publishing settings. This paid operation changes future automation behavior.
Changes a feedback entry's triage status and returns the updated entry. This is a paid write operation.
Rename a GEO project or relink its brand identity. This changes persistent project configuration and requires paid access and a GEO plan.
Enable or disable a tracked prompt, or replace labels on a custom prompt. This changes future scan coverage and requires paid GEO access.
Change a tracked sequence's name, turns, or enabled state. This affects future paid GEO runs.
Update selected fields of an existing Notra post. Markdown changes re-render content; when title is omitted, Notra derives it from the first markdown heading or keeps the existing title if there is no heading. Status changes can publish or unpublish the post, and content or metadata changes may sync a linked GitHub pull request.
Replaces the schedule. Send the full schedule body; fields that are omitted are not preserved from the existing schedule. This paid operation replaces the schedule configuration and can change future generation or automatic publishing behavior.
Updates the name, description, or content of a skill. System skills can be edited but not renamed. This paid operation changes an existing agent skill.
Create, update, or rename a persistent tracked competitor, matching names case-insensitively, and return the full list. Requires paid GEO access.
The Notra integration connects your Dench AI CRM directly to Notra, so agents can read and act on your Notra data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
110 actions are available for agents to invoke on your behalf. Every call runs through Notra's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Notra and click Connect — you'll authorize access through Notra's own sign-in flow. No API keys or code required.
Ask an agent to use Notra in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Notra integration connects your AI CRM to Notra, so AI agents can work with your Notra data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Notra integration currently exposes 110 actions, including Approve GEO Content Brief, Cancel Post Schedule, Create Agent Session, Create Chat, Create Event Trigger, and Create GEO Project. Agents invoke them on your behalf from chat or from automations.
No. You connect Notra from your Dench workspace using Notra's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Notra's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Notra connection from your workspace settings at any time.