POMA Grill for AI agents
Agents read POMA Grill at once. Changes and sends are held for a person's approval by default.
About POMA Grill
POMA Grill is a project-scoped context engine for ingesting documents, managing indexed content, and retrieving prompt-ready context for LLM applications.
What an agent can do in POMA Grill
Every POMA Grill action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in POMA Grill without asking first. 7 actions.
- Get Bucket Ingest TaskGet the current state, progress, processing rate, credential status, and recent failures for a POMA Grill bucket-ingest task.
- Get DocumentGet metadata for one indexed document by its document ID.
- Get Ingest JobGet 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.
- List Bucket Ingest FailuresReturn one page of failed items for a bucket ingest task, ordered by item ID, with an opaque cursor for the next page.
- List DocumentsList one page of document metadata from the connected project.
- Preview Bucket IngestValidate 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.
- Search DocumentsSearch indexed content across the project or within one document, returning either prompt-ready context or structured matching chunks.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 10 actions.
- Cancel Bucket Ingest TaskIrreversibly cancel a non-terminal POMA Grill bucket-ingest task. Already terminal tasks cannot be cancelled.
- Cancel Ingest JobRequest best-effort cancellation and removal of an ingestion job. A successful response does not guarantee that completed job metadata disappears.
- Delete DocumentPermanently delete one deliberately selected indexed document, including its vectors and stored assets. This action cannot be undone.
- Ingest DocumentUpload one file or provide one public remote URL for asynchronous indexing, and return the ingestion job ID to poll with Get Ingest Job.
- Pause Bucket Ingest TaskPause 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.
- Resume Bucket Ingest TaskResume a bucket ingest task paused by the user, restoring its pre-pause state and waking processing for the next scheduler tick.
- Retry Bucket Ingest FailuresRetry all or selected failed items in a bucket ingest task that is in done_with_errors or materialising. Refresh purged source credentials first.
- Submit Bucket IngestCreate 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 input
- Update Bucket Ingest CredentialsReplace and validate the source credentials for an active bucket ingest task. A task paused for a source credential error resumes materialising on success.
- Update Document AttributesSet, change, or remove selected typed attributes on one indexed document. Null attribute values remove those attributes; omitted names are unchanged.
Changes wait in Needs you
Changes and sends in POMA Grill are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
POMA Grill questions
Can an agent change data in POMA Grill on its own?
Not by default. Changes and sends in POMA Grill are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in POMA Grill?
This connector lists 7 read actions. Reads run at once, without waiting for approval.
How does POMA Grill connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.