Meta · Arazzo Workflow

Meta Decommission User Account

Version 1.0.0

Snapshot a user, remove them from a custom audience, then delete the test user.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub AdvertisingAnalyticsArtificial IntelligenceMessagingSocialSocial-MediaVirtual RealityArazzoWorkflows

Provider

meta

Workflows

decommission-user-account
Snapshot a user, remove from an audience, then delete the test user.
Reads the user, removes them from the custom audience, then deletes the test user account.
3 steps inputs: accessToken, customAudienceId, fields, userId outputs: deleted, removed, userId
1
snapshotUser
Read the User node to capture a final snapshot before removal.
2
removeFromAudience
Remove the user from the custom audience so they are no longer targeted. The remove edge is declared without a request body in the spec.
3
deleteUser
Delete the test user account to complete decommissioning.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Meta Decommission User Account
  summary: Snapshot a user, remove them from a custom audience, then delete the test user.
  description: >-
    An offboarding flow for a test user. It first reads the User node to capture
    a final snapshot, then removes the user from a custom audience so they are no
    longer targeted, and finally deletes the test user account. Ordering the
    deletion last ensures the audience cleanup runs while the user still exists.
    Every step inlines its request so the flow can be read and executed without
    opening the underlying OpenAPI description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-400.60
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-400.60
      capability_name: Digital Marketing Management
      spec: meta-custom-audiences-api-openapi.yml
      confidence: 0.75
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: customAudiencesApi
  url: ../openapi/meta-custom-audiences-api-openapi.yml
  type: openapi
- name: usersApi
  url: ../openapi/meta-users-api-openapi.yml
  type: openapi
workflows:
- workflowId: decommission-user-account
  summary: Snapshot a user, remove from an audience, then delete the test user.
  description: >-
    Reads the user, removes them from the custom audience, then deletes the
    test user account.
  inputs:
    type: object
    required:
    - accessToken
    - userId
    - customAudienceId
    properties:
      accessToken:
        type: string
        description: A Meta Graph API user access token.
      userId:
        type: string
        description: The id of the test user to decommission.
      customAudienceId:
        type: string
        description: The custom audience to remove the user from.
      fields:
        type: string
        description: Comma-separated fields to capture in the final snapshot.
  steps:
  - stepId: snapshotUser
    description: >-
      Read the User node to capture a final snapshot before removal.
    operationId: getUser
    parameters:
    - name: user-id
      in: path
      value: $inputs.userId
    - name: fields
      in: query
      value: $inputs.fields
    - name: access_token
      in: query
      value: $inputs.accessToken
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      userId: $response.body#/id
      name: $response.body#/name
  - stepId: removeFromAudience
    description: >-
      Remove the user from the custom audience so they are no longer targeted.
      The remove edge is declared without a request body in the spec.
    operationId: removeUsersFromCustomAudience
    parameters:
    - name: custom-audience-id
      in: path
      value: $inputs.customAudienceId
    - name: access_token
      in: query
      value: $inputs.accessToken
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      removed: $response.body#/success
  - stepId: deleteUser
    description: >-
      Delete the test user account to complete decommissioning.
    operationId: deleteUser
    parameters:
    - name: user-id
      in: path
      value: $steps.snapshotUser.outputs.userId
    - name: access_token
      in: query
      value: $inputs.accessToken
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      deleted: $response.body#/success
  outputs:
    userId: $steps.snapshotUser.outputs.userId
    removed: $steps.removeFromAudience.outputs.removed
    deleted: $steps.deleteUser.outputs.deleted

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/meta-decommission-user-account-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.