Cancel Bucket Ingest Task
Irreversibly cancel a non-terminal POMA Grill bucket-ingest task. Already terminal tasks cannot be cancelled.
ActionTry it
Integrate POMA Grill
with your AI CRM
POMA Grill is a project-scoped context engine for ingesting documents, managing indexed content, and retrieving prompt-ready context for LLM applications.
Explore Triggers and Actions
Cancel Ingest Job
Request best-effort cancellation and removal of an ingestion job. A successful response does not guarantee that completed job metadata disappears.
ActionTry it
Delete Document
Permanently delete one deliberately selected indexed document, including its vectors and stored assets. This action cannot be undone.
ActionTry it
Get Bucket Ingest Task
Get the current state, progress, processing rate, credential status, and recent failures for a POMA Grill bucket-ingest task.
ActionTry it
Get Document
Get metadata for one indexed document by its document ID.
ActionTry it
Get Ingest Job
Get an ingestion job's current status and usage; poll this after Ingest Document until status is done, failed, or blocked. Grill jobs may pass through indexing before reaching a terminal state.
ActionTry it
Ingest Document
Upload one file or provide one public remote URL for asynchronous indexing, and return the ingestion job ID to poll with Get Ingest Job.
ActionTry it
List Bucket Ingest Failures
Return one page of failed items for a bucket ingest task, ordered by item ID, with an opaque cursor for the next page.
ActionTry it
List Documents
List one page of document metadata from the connected project.
ActionTry it
Pause Bucket Ingest Task
Pause a non-terminal bucket ingest task in paused_user state. Processing halts on the next scheduler tick while the task continues to occupy its account's active-task slot.
ActionTry it
Preview Bucket Ingest
Validate S3 or GCS credentials and preview matching source objects without creating a bucket-ingest task. Sensitive credentials are sent to POMA and exposed to the action execution environment.
ActionTry it
Resume Bucket Ingest Task
Resume a bucket ingest task paused by the user, restoring its pre-pause state and waking processing for the next scheduler tick.
ActionTry it
Retry Bucket Ingest Failures
Retry all or selected failed items in a bucket ingest task that is in done_with_errors or materialising. Refresh purged source credentials first.
ActionTry it
Search Documents
Search indexed content across the project or within one document, returning either prompt-ready context or structured matching chunks.
ActionTry it
Submit Bucket Ingest
Create an asynchronous task to ingest matching objects from an S3 or GCS bucket into POMA Grill, optionally delivering results to another bucket. Source and destination credentials are sensitive inputs sent to POMA and exposed to the action execution environment.
ActionTry it
Submit Bucket Ingest Eco (Legacy)
Deprecated compatibility route for creating a POMA Grill bucket-ingest task. Use Submit Bucket Ingest for new calls; POMA documents both routes as behaviorally identical.
ActionTry it
Update Bucket Ingest Credentials
Replace and validate the source credentials for an active bucket ingest task. A task paused for a source credential error resumes materialising on success.
ActionTry it
Update Document Attributes
Set, change, or remove selected typed attributes on one indexed document. Null attribute values remove those attributes; omitted names are unchanged.
ActionTry it
How the POMA Grill integration works
The POMA Grill integration connects your Dench AI CRM directly to POMA Grill, so agents can read and act on your POMA Grill data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
18 actions are available for agents to invoke on your behalf. Every call runs through POMA Grill's own authorization, scoped to the account you connect.
Set up POMA Grill in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find POMA Grill and click Connect — you'll authorize access through POMA Grill's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use POMA Grill in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the POMA Grill integration work with Dench?
The Dench POMA Grill integration connects your AI CRM to POMA Grill, so AI agents can work with your POMA Grill 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.
What actions can AI agents perform with POMA Grill via Dench?
The POMA Grill integration currently exposes 18 actions, including Cancel Bucket Ingest Task, Cancel Ingest Job, Delete Document, Get Bucket Ingest Task, Get Document, and Get Ingest Job. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect POMA Grill to Dench?
No. You connect POMA Grill from your Dench workspace using POMA Grill's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the POMA Grill integration secure?
Connections are authorized through POMA Grill's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the POMA Grill connection from your workspace settings at any time.