deixic
Log inRequest a demo

← Docs

Docs · Connector reference

Cloudflare Email connector reference

Operations, inputs, troubleshooting, and questions for the Cloudflare Email connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Cloudflare Email connection

  1. Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
  2. Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
  3. Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
  4. Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Action
Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.
OperationEffectApprovalProvider permissionsInputs
ReplyActionBy policyNone named5

Inputs by operation

Reply Action
Inputs for Cloudflare-Email Reply
InputRequirementAccepted value
fromRequiredstringMaximum characters: 254
headersRequiredobject
subjectRequiredstringMinimum characters: 1Maximum characters: 520
textRequiredstringMinimum characters: 1Maximum characters: 32768
toRequiredstringMinimum characters: 3Maximum characters: 254

When the Cloudflare Email task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the bearer token connection and its access to the specific resource; a successful connection does not establish access to every object.

Compare the lookup against one known record first, and keep an empty response separate from a permissions error.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Cloudflare Email connector

Can I use my existing agent with Cloudflare Email?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Cloudflare Email?

This connector supports 1 action, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Cloudflare Email?

Prepare API token with Email Sending permission, Cloudflare account ID; the connection uses Bearer token, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Cloudflare Email keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.

Cloudflare Email connector overviewDocsAll connectors