Cloudflare integration overview

Overview

Cloudflare provides a range of internet services, including content delivery network (CDN) services, cloud cybersecurity, DDoS mitigation, and domain registration.

Persona’s Cloudflare integration brings Cloudflare account membership data into Persona workflows so teams can automate access checks and reduce manual follow-ups during onboarding, investigations, or internal reviews. With it, you can look up which Cloudflare accounts a user can access, pull detailed membership context, and programmatically respond to pending account invitations.

Benefits

Centralized Access Context: Surface Cloudflare membership details (like account information, roles, and permissions) inside Persona so reviewers have the right context when making decisions.

Automated Access Reviews: Automatically look up memberships and filter results (for example, by status) to support repeatable, policy-driven checks in workflows.

Faster Provisioning & Offboarding: Accept or reject pending Cloudflare account invitations directly from Persona, helping teams close the loop without manual clicks across tools.

Integration Features

Persona’s Cloudflare integration helps teams manage Cloudflare membership-related workflows directly from Persona. Key capabilities include:

• List memberships: Retrieve the Cloudflare account memberships a user can access, with optional filtering, sorting, and pagination.
• Retrieve membership details: Fetch a specific membership to access the latest account and access context in downstream workflow steps.
• Respond to invitations: Accept or reject a pending Cloudflare account invitation to support closed-loop provisioning workflows.

Setting up the Cloudflare integration

Prerequisites

To set up the Cloudflare integration, ensure you have:

• Admin access to your Cloudflare account
• Necessary API permissions to access Cloudflare credentials

Setting up the Cloudflare Credentials

1. In the Cloudflare dashboard, create an API token with permissions appropriate for the membership actions you plan to run. (Cloudflare recommends using API tokens whenever possible.)
2. In the Persona Dashboard, navigate to Integrations > Marketplace and select Cloudflare.
3. Click Add Credential.
4. Enter a Nickname for Credential so teammates can recognize this connection later.
5. Follow the prompts to add your Cloudflare API token, then save the credential.
6. Click Test to confirm the credential is working.

Using the Cloudflare integration in a workflow

1. Create a new workflow, or open an existing workflow you’d like to update.
2. Add a new action step > Integrations.
3. Select the Cloudflare integration and choose your saved Cloudflare credential.
4. Select the operation you want to run (for example, List Memberships or Update Membership) and configure the input fields.
5. Save and publish the workflow.

Cloudflare Operations Overview

In addition to syncing field values, Persona can list memberships, retrieve membership details, and accept or reject account invitations using Cloudflare’s API. These actions support seamless two-way workflows, letting teams manage investigations without switching platforms.

See below for a comprehensive list of available Workflow Action steps and possible configurations for the Cloudflare integration:

List Memberships Workflow Action Step

Lists the Cloudflare account memberships the connected user can access. This is useful when you need to discover relevant accounts dynamically (for example, during onboarding) or narrow results to specific membership states like pending invitations.

Configuration Steps:

• Optionally add:
  • Account name filter
  • Name filter
  • Status (accepted, pending, rejected)
  • Sorting (field + direction)
  • Pagination (page and results per page)

Retrieve Membership Workflow Action Step

Retrieves a single Cloudflare membership by its identifier so you can access the latest details for that membership. This is helpful when a workflow already has a membership ID (for example, from a prior step) and needs authoritative account context—such as roles, permissions, or current status—before taking action.

Configuration Steps:

• Provide values for required fields:
  • Membership ID

Update Membership Workflow Action Step

Updates a pending membership by responding to an account invitation. In practice, this lets you accept or reject an invitation as part of a controlled workflow—so teams can operationalize provisioning decisions and keep Cloudflare access aligned with internal policy.

Configuration Steps:

• Provide values for required fields:
  • Membership ID
  • Status (accepted or rejected)

FAQs

What Cloudflare data can Persona access with this integration?

Persona can retrieve Cloudflare membership information, including membership status and related account context (such as account details, roles, permissions, and policies) when available in the membership response.

What do membership statuses mean in Cloudflare?

Memberships can be accepted, pending, or rejected. Pending memberships typically indicate an outstanding invitation that can be responded to via the Update Membership action.

Can I limit which memberships are returned when listing memberships?

Yes. When listing memberships, you can optionally filter by fields like account name or status, and you can also sort and paginate results to handle larger environments.