Skip to main content

Temporal integration

Developer tools connector, available on Zeplik

Temporal is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Temporal and Zeplik can act on your software development for you: Cloud-native workflow orchestration platform for building reliable distributed applications. You stay in the conversation while the assistant does the work in Temporal directly.

Zeplik exposes 16 read actions and 33 write actions for Temporal. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Temporal without your consent.

Try Temporal on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with Temporal

Read from Temporal (16)

Runs automatically in any conversation.

  • Count workflows

    Return an approximate count of Workflow Executions matching a Temporal Visibility query, including supported grouped counts. Requires Namespace Read access.

  • Describe batch operation

    Return progress, state, selection query, type, and failure counts for one batch operation in an authorized Temporal Cloud Namespace. Requires Namespace Read access.

  • Describe namespace

    Return one Temporal Cloud Namespace's configuration, resource version, routing endpoints, state, limits, and capacity. Requires Namespace Read access.

  • Describe workflow

    Return configuration, status, pending work, callbacks, and child state for one Workflow Execution in an authorized Temporal Cloud Namespace. Omit run_id to describe the current run. Requires Namespace Read access.

  • Get async operation

    Return the current state and failure details of a Temporal Cloud asynchronous operation.

  • Get export sink

    Return one Temporal Cloud Workflow History export sink, including its resource version, destination configuration, state, and health. Requires Namespace Read access.

  • Get namespace capacity

    Return a Temporal Cloud Namespace's capacity mode, available limits, and seven-day actions-per-second statistics. Requires Namespace Read access.

  • Get workflow history

    Return one page of a Temporal Workflow Execution's Event History in forward or reverse order. Requires Namespace Read access.

  • List archived workflows

    Return one page of archived Workflow Executions matching an exact Temporal Visibility query. Requires Namespace Read access and a Namespace deployment with archival visibility configured and available; the probed Namespace returned HTTP 403 even with inherited Namespace Admin access.

  • List batch operations

    Return one page of batch operations in an authorized Temporal Cloud Namespace. Requires Namespace Read access.

  • List export sinks

    Return one page of Workflow History export sinks configured on a Temporal Cloud Namespace. Requires Namespace Read access.

  • List namespace assignments

    Return one page of users, User Groups, or Service Accounts assigned to a Temporal Cloud Namespace. Requires Namespace Read access.

and 4 more.

Act in Temporal (33)

Runs only after you enable write access.

  • Batch cancel workflows

    Request cancellation of selected Temporal Workflows. Cancellation is cooperative: Workflow code can perform cleanup and external side effects before closing. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the observed scope; its approximate count is not a hard upper bound because matches can change. Use explicit target_executions when a fixed cardinality bound is required. A stable job_id identifies this operation but does not make retries idempotently successful. After an ambiguous timeout, a retry may return 409 because Temporal rejects duplicate job IDs. Call DESCRIBE_BATCH_OPERATION with the same namespace_id and job_id to reconcile before creating any other batch operation. Requires Namespace Write access.

  • Batch delete workflows

    WARNING: Permanently delete selected Temporal Workflow Executions and their Event Histories. This cannot be undone. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the observed scope; its approximate count is not a hard upper bound because matches can change. Use explicit target_executions when a fixed cardinality bound is required. A stable job_id identifies this operation but does not make retries idempotently successful. After an ambiguous timeout, a retry may return 409 because Temporal rejects duplicate job IDs. Call DESCRIBE_BATCH_OPERATION with the same namespace_id and job_id to reconcile before creating any other batch operation. Requires Namespace Write access.

  • Batch reset workflows

    WARNING: Irreversibly reset selected Temporal Workflows. Each successful reset terminates the current run and creates a new run; replay and reapplied events can repeat application code and external side effects. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the observed scope; its approximate count is not a hard upper bound because matches can change. Use explicit target_executions when a fixed cardinality bound is required. A stable job_id identifies this operation but does not make retries idempotently successful. After an ambiguous timeout, a retry may return 409 because Temporal rejects duplicate job IDs. Call DESCRIBE_BATCH_OPERATION with the same namespace_id and job_id to reconcile before creating any other batch operation. Requires Namespace Write access.

  • Batch signal workflows

    Send a named Signal to selected Temporal Workflows. Signal handlers run application code and can cause arbitrary, non-idempotent external side effects. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the observed scope; its approximate count is not a hard upper bound because matches can change. Use explicit target_executions when a fixed cardinality bound is required. A stable job_id identifies this operation but does not make retries idempotently successful. After an ambiguous timeout, a retry may return 409 because Temporal rejects duplicate job IDs. Call DESCRIBE_BATCH_OPERATION with the same namespace_id and job_id to reconcile before creating any other batch operation. Requires Namespace Write access.

  • Batch terminate workflows

    WARNING: Irreversibly terminate selected Temporal Workflows immediately; Workflow cleanup code does not run. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the observed scope; its approximate count is not a hard upper bound because matches can change. Use explicit target_executions when a fixed cardinality bound is required. A stable job_id identifies this operation but does not make retries idempotently successful. After an ambiguous timeout, a retry may return 409 because Temporal rejects duplicate job IDs. Call DESCRIBE_BATCH_OPERATION with the same namespace_id and job_id to reconcile before creating any other batch operation. Requires Namespace Write access.

  • Batch update workflow options

    Update typed execution options on selected Temporal Workflows. Worker routing, task priority, and virtual-time changes can cause application and external side effects. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the observed scope; its approximate count is not a hard upper bound because matches can change. Use explicit target_executions when a fixed cardinality bound is required. A stable job_id identifies this operation but does not make retries idempotently successful. After an ambiguous timeout, a retry may return 409 because Temporal rejects duplicate job IDs. Call DESCRIBE_BATCH_OPERATION with the same namespace_id and job_id to reconcile before creating any other batch operation. Requires Namespace Write access.

  • Cancel workflow

    Irreversibly request cooperative cancellation of a running Temporal Workflow Execution. Temporal records a cancellation-requested event and schedules a Workflow Task, but the Workflow may delay or ignore cancellation depending on its code. A request for an already-closed Workflow succeeds. Requires Namespace Write access.

  • Create export sink

    Create a persistent Temporal Cloud Workflow History export sink asynchronously. Requires Namespace Admin access. Warning: an enabled sink writes closed Workflow Histories to external storage on an ongoing schedule and may incur storage costs. Validate the destination first, use a disposable sink for testing, and arrange teardown.

  • Delete export sink

    Delete a Temporal Cloud Workflow History export sink asynchronously. Requires Namespace Admin access. WARNING: this irreversibly stops future exports from the sink. Files already exported to external storage remain there and must be managed separately. Confirm the Namespace, sink name, and current resource version before calling.

  • Delete namespace

    Permanently and irreversibly delete a Temporal Cloud Namespace and all of its Workflow data asynchronously. WARNING: there is no recovery or undo. Use only for a verified disposable Namespace after confirming its full ID, contents, latest resource version, and that deletion protection is disabled.

  • Failover namespace region

    Switch a multi-region Temporal Cloud Namespace's active region asynchronously. WARNING: This operation disrupts current Namespace routing while failover completes. Require explicit approval and a documented rollback or failback plan before calling it.

  • Move namespace to project

    Move a Temporal Cloud Namespace to another Project asynchronously. WARNING: this disruptive operation can change inherited access and connectivity. Verify the source and destination Projects, preserve required connectivity rules, and obtain explicit approval before calling it.

and 21 more.

How to connect Temporal

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Temporal immediately.

  2. Connect Temporal

    Open Settings and go to Connectors, then press Connect on Temporal. You can also connect from the Temporal page in the app.

  3. Add your Temporal API key

    Paste your Temporal API key when prompted. Zeplik stores it securely on the server and starts working with Temporal right away.

Frequently asked questions

Can I use Temporal with Zeplik?
Yes. Temporal is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Temporal account inside any conversation.
What can Zeplik do with Temporal?
Once connected, Zeplik has 16 read and 33 write actions for Temporal. Cloud-native workflow orchestration platform for building reliable distributed applications.
How do I connect Temporal to Zeplik?
You connect Temporal by pasting your own Temporal API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in Temporal without asking?
No. Zeplik reads from Temporal by default. Any action that changes data in Temporal requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting Temporal cost?
Connecting Temporal is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related developer tools integrations

More on Zeplik

Connect Temporal to your AI assistant

Every model, one chat. Bring Temporal into Zeplik and let the assistant do the work.