developer tools

Add Temporal to your AI agent

Cloud-native workflow orchestration platform for building reliable distributed applications

Things your agent can do in Temporal
49

Things your AI can do in Temporal

Your FormWise AI can handle any of these in Temporal — on its own, without you needing to click a button.

  • 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.

  • Count Workflows

    Return an approximate count of Workflow Executions matching a Temporal Visibility query, including supported grouped counts. Requires Namespace Read 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.

  • 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.

Show 37 more things it can do
  • 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.

  • Fail Over 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.

  • 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.

  • List Namespaces

    Return one page of Temporal Cloud Namespaces visible to the API-key identity, optionally filtered by name or Project.

  • List Cloud Regions

    List currently available Temporal Cloud regions for Namespace placement.

  • List Workflows

    Search one page of Workflow Executions in an authorized Temporal Cloud Namespace using Temporal Visibility query syntax. Requires Namespace Read access.

  • 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.

  • Pause Workflow

    Pause one Temporal Workflow Execution. Temporal changes its status to PAUSED, records a WORKFLOW_EXECUTION_PAUSED event, stops dispatching new Workflow and Activity Tasks, pauses executing Activities, and rejects Queries and Updates; an executing Workflow Task may still complete and server-side events continue. This operational side effect can halt business processing. Always call UNPAUSE_WORKFLOW during teardown, even if a later step fails. Requires Namespace Write access. This Temporal API is experimental.

  • Query Workflow

    Run a synchronous, read-only Query handler against one Temporal Workflow Execution. The handler runs in Workflow context but cannot mutate Workflow state. Requires Namespace Read access.

  • Register Namespace

    Create a billable, persistent Temporal Cloud Namespace asynchronously and return its full Namespace ID and operation ID. The name and replicas are immutable, and custom Search Attributes cannot be deleted. Use a unique disposable name for testing and arrange teardown only after creation completes.

  • Remove Namespace Access

    Remove one user's, user group's, or service account's direct permission on a Temporal Cloud Namespace by setting PERMISSION_UNSPECIFIED. Requires Namespace Admin. WARNING: this can immediately remove access or lock out the selected identity; verify inherited access and never remove the caller's or sole administrator's access.

  • Rename Custom Search Attribute

    Rename one custom Search Attribute in a Temporal Cloud Namespace asynchronously. This is a potentially breaking schema mutation: Temporal does not rewrite application Visibility queries or dashboards that reference the old name. Verify all consumers and use the latest Namespace resource version before starting the rename.

  • Replace Workflow

    Replace a running Workflow Execution with a new execution using the same Workflow ID. WARNING: if that ID is running, Temporal irreversibly terminates the existing execution before starting the replacement. This may interrupt in-flight work, and the new Workflow may cause arbitrary external side effects. Use only when termination is explicitly intended, and use request_id for idempotent retries. Requires Namespace Write access.

  • Reset Workflow

    WARNING: Irreversibly reset a Temporal Workflow to a selected Workflow Task event. Temporal terminates the current run and creates a new run; replay and reapplied events can repeat application code and external side effects. Verify the source run, event ID, and reapply policy before calling.

  • Set Namespace Access

    Set one user's, user group's, or service account's direct ADMIN, WRITE, or READ permission on a Temporal Cloud Namespace. The new permission replaces that principal's current direct access; setting a lower permission may lock out the caller or the Namespace's sole admin. Requires Namespace Admin.

  • Signal With Start Workflow

    Atomically signal a running Temporal Workflow or start and signal it when absent. This may run application code and trigger external side effects; use a stable request_id when retrying the same intent. The TERMINATE_EXISTING conflict policy and deprecated TERMINATE_IF_RUNNING reuse policy can terminate a running execution before starting and signaling its replacement.

  • Signal Workflow

    Send an asynchronous Signal to one running Temporal Workflow Execution. This records a history event, schedules Workflow code, and may trigger arbitrary external business side effects. Temporal's successful response only confirms acceptance, not handler completion. Use request_id to make retries idempotent. Requires Namespace Write access.

  • Start or Get Workflow

    Start a Workflow Execution, or return the already-running execution when the Workflow ID conflicts. This action never replaces the running execution. The response has started=false when it returns the existing execution. Starting a Workflow dispatches application code and may cause arbitrary external side effects. Use request_id for idempotent retries. Requires Namespace Write access.

  • Start Workflow

    Start a new Workflow Execution in an authorized Temporal Cloud Namespace. The request fails if the Workflow ID is already running; use Start or Get Workflow or Replace Workflow only when those different conflict semantics are intended. This dispatches application code and may cause arbitrary external side effects. Use request_id for idempotent retries. Requires Namespace Write access.

  • Stop Batch Operation

    Request that Temporal stop an in-progress batch operation. This does not roll back Workflows already processed by the batch: their cancellations, terminations, signals, deletions, resets, or option changes remain in effect. Requires Namespace Write access.

  • Terminate Workflow

    Immediately and irreversibly terminate one Temporal Workflow Execution. WARNING: termination bypasses cooperative cancellation and Workflow cleanup logic, so finally blocks, compensation, and pending work may not run. Use cancellation instead when the Workflow can clean up safely. Requires Namespace Write access.

  • Trigger Workflow Rule

    Trigger an existing configured Temporal Workflow Rule against one Workflow Execution. This irreversible request evaluates the rule and, when its conditions match, may run configured actions with destructive or arbitrary external side effects. Verify the Workflow and rule before calling; do not test against production or an unknown rule. A successful request can return applied=false when the rule conditions do not match. Requires Namespace Write access.

  • Unpause Workflow

    Resume a paused Temporal Workflow Execution. Unpausing changes its status to running, records an unpaused history event, and resumes application code in Workflow and Activity Tasks, which may produce external side effects. Use request_id for idempotent retries. This Temporal API is experimental and requires Namespace Write access.

  • Update Export Sink

    Update an existing Temporal Cloud Workflow History export sink asynchronously using optimistic concurrency. WARNING: this replaces the sink's destination configuration or enabled state for future exports and may redirect or stop Workflow History delivery; already exported files are not moved or undone. Confirm the complete current specification, destination, and resourceVersion before calling.

  • Update Namespace

    Update a Temporal Cloud Namespace specification asynchronously using the latest resource version for optimistic concurrency. WARNING: this full-spec replacement can change retention, regions, capacity, authentication, deletion protection, and high-availability behavior; newly added custom Search Attributes cannot be deleted. Preserve every unchanged field and verify API-key access and deletion protection before calling. Requires Namespace Admin access.

  • Update Namespace Tags

    Upsert or permanently remove tags on a Temporal Cloud Namespace asynchronously; removed tags no longer exist on the Namespace. At least one of tags_to_upsert or tags_to_remove must be non-empty, and the same key cannot appear in both. The API-key owner must be a Global Admin or Account Owner; Namespace Admin access alone is insufficient.

  • Update Workflow

    Send a durable Update to one Temporal Workflow Execution and wait for the requested lifecycle stage. The Workflow handler may mutate state and cause arbitrary external business side effects. Reuse update_id only when retrying the same intended Update. An admitted or accepted response can omit outcome; the returned update_ref identifies the still-running Update. Requires Namespace Write access.

  • Update Workflow Options

    Update selected options on one Temporal Workflow Execution using an exact protobuf FieldMask. This mutation can reroute Workflow Tasks to different Workers, change task priority, or alter virtual-time behavior and thereby cause application side effects. Use only on an intended execution, capture the prior options, and restore them when testing. Requires Namespace Write access.

  • Validate Export Sink

    Validate a Temporal Cloud Workflow History export sink configuration. WARNING: this is not read-only; Temporal writes an empty test object to the configured external bucket or container. Use only an owner-approved disposable bucket or container.

Built for the way you actually work

No code, no engineers

Connect in a few clicks and start using your AI right away. If you can use the apps you already love, you can do this.

Sounds like you, not like a bot

Train your AI on your offer, your voice, and the way you actually talk to clients — it picks up where you leave off.

Plugs into the stack you already use

No need to rip out your CRM, your scheduler, or your email tool. Your AI works inside the apps running your business today.

Your data stays yours

Client conversations, lists, and credentials are scoped to your workspace. Nothing gets shared, sold, or used to train anyone else’s AI.

What you can do once Temporal is connected

Onboard new clients without lifting a finger

When someone signs up, your AI greets them, sets up their next step in Temporal, and keeps the momentum going — even at 2am.

Reply to leads in seconds, not days

Your AI watches Temporal for new inquiries, answers questions in your voice, and books the call before they cool off.

Get your weekends back

Hand off the repetitive Temporal work — follow-ups, reminders, updates, simple admin — and stop being the bottleneck in your own business.

How to connect Temporal to your agent

  1. 1

    Start using FormWise for free

    Sign up in under a minute.

  2. 2

    Find Temporal in your connected apps

    Inside FormWise, go to Settings → Connected Services and look for Temporal.

  3. 3

    Hit "Connect"

    Click "Connect Temporal" and log in like you normally would. We only ask for the permissions your AI actually needs.

  4. 4

    Tell your AI what to do in Temporal

    Build a quick AI Agent (it's like writing instructions, not code), and pick the Temporal actions you want your AI to handle.

  5. 5

    Watch it run

    Send it a real-world task and watch your AI take care of Temporal for you. Tweak the wording until it feels just right.

Powered by the AI you already trust

Your Temporal workflow runs on the same world-class AI used by ChatGPT, Claude, and Gemini. We handle the technical part — you just tell your AI what to do, in plain English.

  • OpenAI
  • Anthropic Claude
  • Google Gemini

Questions other Temporal users had before signing up

Do I need to know how to code?

Not even a little. If you can use Temporal today, you can set this up. You'll connect Temporal, tell your AI what it should help with, and you're live. The whole thing is built for coaches, course creators, agencies, and operators — not engineers.

Will my clients know they're talking to an AI?

Only if you want them to. Your FormWise AI is trained on your voice, your offer, and the way you actually communicate — so it sounds like a thoughtful team member, not a clunky chatbot. Most people can't tell.

Can I make it sound like me?

Yes. You can give your AI examples of how you write, the questions you usually ask new clients, the way you handle objections, and the language you use about your offer. The more you give it, the more it sounds like you wrote it.

What if I want to take over a conversation?

You're always in control. You can step in at any point, take over from your AI, or stop it from sending messages until you've reviewed them. Think of it as a teammate, not a replacement.

Is my client data safe?

Yes. Your Temporal login and client information stay scoped to your workspace. We don't sell it, we don't share it, and we don't use your data to train anyone else's AI. You can disconnect Temporal or delete everything any time.

What happens when Temporal updates their app?

We handle it. When Temporal adds new features or changes how something works, we update the integration in the background. You don't have to do anything — your AI just keeps working.

How fast can I actually get this running?

Most people are up and running the same day they sign up. Connecting Temporal takes a few minutes. Teaching your AI to handle the work the way you'd want it done is the part worth slowing down for.

What is FormWise?

FormWise is the AI agent builder for coaches, course creators, and agencies. You connect the apps you already use — like Temporal — train your AI on your offer and voice, and let it handle the work you've been doing manually: onboarding, follow-ups, support, admin. No code, no developers, no engineering team required.

Can I sell AI agents to my clients?

Yes. A lot of FormWise users build AI assistants and sell them as part of their offer — done-for-you AI setups, white-label assistants for client businesses, custom GPTs trained on a client's brand. You can charge a setup fee, a monthly retainer, or both.

Can I embed my AI on my website or in my course?

Yes. Every AI you build in FormWise can be embedded on your site, dropped into your course platform, or shared as a standalone link. Your clients and students just open it like any other web page — no app to download, no login hoops.

Do I need to know anything about AI to use this?

No. If you can describe what you want your AI to do in plain English — "greet new clients, ask these 3 questions, book them a call" — FormWise can build it. We handle the models, the prompts, the connections. You handle the part you already know: what your business actually needs.

About Temporal on FormWise

Cloud-native workflow orchestration platform for building reliable distributed applications

Connect Temporal once and your FormWise AI gets 49 things it can do inside it. That means your AI can handle the Temporal work in your business — the messages, the updates, the follow-ups, the admin — the way you would, just faster and around the clock.

You don't need to know how any of it works under the hood. We take care of keeping the connection alive, retrying if something fails, and making sure your data only ever moves where you tell it to.

New to Temporal? Take a look at temporal.io.

Stop doing the Temporal work yourself

Hand it off to an AI assistant that sounds like you, works around the clock, and never forgets a follow-up. Free to start.