Adobe Launch · Arazzo Workflow

Adobe Launch Create and Verify a Data Element

Version 1.0.0

Create a data element under a property, then read it back to confirm it persisted.

1 workflow 1 source API 1 provider
View Spec View on GitHub Data CollectionEdge NetworkEvent ForwardingMarketing TechnologyTag ManagementArazzoWorkflows

Provider

adobe-launch

Workflows

create-and-verify-data-element
Create a data element and immediately read it back by id.
Creates a data element under the supplied property and verifies persistence by retrieving it, surfacing its id and attributes as workflow outputs.
2 steps inputs: accessToken, apiKey, dataElementName, delegateDescriptorId, extensionId, imsOrgId, propertyId outputs: dataElementId, name
1
createDataElement
Create a data element under the property, linked to its extension.
2
getDataElement
Read the data element back by id to confirm it persisted.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Adobe Launch Create and Verify a Data Element
  summary: Create a data element under a property, then read it back to confirm it persisted.
  description: >-
    A data element is the reusable variable backbone of an Adobe Experience
    Platform Launch (Tags) property. This workflow creates a data element under
    a property, linked to the extension that provides it, and then retrieves the
    newly created data element by id to confirm it was stored with the expected
    attributes. Each request is written inline using the JSON:API document shape
    these endpoints require.
  version: 1.0.0
sourceDescriptions:
- name: dataElementsApi
  url: ../openapi/adobe-launch-data-elements-api-openapi.yml
  type: openapi
workflows:
- workflowId: create-and-verify-data-element
  summary: Create a data element and immediately read it back by id.
  description: >-
    Creates a data element under the supplied property and verifies persistence
    by retrieving it, surfacing its id and attributes as workflow outputs.
  inputs:
    type: object
    required:
    - accessToken
    - apiKey
    - imsOrgId
    - propertyId
    - dataElementName
    - delegateDescriptorId
    - extensionId
    properties:
      accessToken:
        type: string
        description: OAuth 2.0 Server-to-Server bearer access token from Adobe Developer Console.
      apiKey:
        type: string
        description: Client ID credential sent as the x-api-key header.
      imsOrgId:
        type: string
        description: Adobe Organization ID sent as the x-gw-ims-org-id header.
      propertyId:
        type: string
        description: The property the data element is created under.
      dataElementName:
        type: string
        description: Human-readable name for the data element.
      delegateDescriptorId:
        type: string
        description: Delegate descriptor id identifying the data element type.
      extensionId:
        type: string
        description: Id of the extension that provides this data element.
  steps:
  - stepId: createDataElement
    description: Create a data element under the property, linked to its extension.
    operationId: createDataElement
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: x-api-key
      in: header
      value: $inputs.apiKey
    - name: x-gw-ims-org-id
      in: header
      value: $inputs.imsOrgId
    - name: propertyId
      in: path
      value: $inputs.propertyId
    requestBody:
      contentType: application/vnd.api+json
      payload:
        data:
          type: data_elements
          attributes:
            name: $inputs.dataElementName
            delegate_descriptor_id: $inputs.delegateDescriptorId
            storage_duration: pageview
            enabled: true
          relationships:
            extension:
              data:
                id: $inputs.extensionId
                type: extensions
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      dataElementId: $response.body#/data/id
  - stepId: getDataElement
    description: Read the data element back by id to confirm it persisted.
    operationId: getDataElement
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: x-api-key
      in: header
      value: $inputs.apiKey
    - name: x-gw-ims-org-id
      in: header
      value: $inputs.imsOrgId
    - name: dataElementId
      in: path
      value: $steps.createDataElement.outputs.dataElementId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      dataElementId: $response.body#/data/id
      name: $response.body#/data/attributes/name
  outputs:
    dataElementId: $steps.getDataElement.outputs.dataElementId
    name: $steps.getDataElement.outputs.name

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/adobe-launch-create-and-verify-data-element-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.