Skip to main content
Our docs redesign is live!

Automate Recipe for Content Type Propagation

Frequently asked questions

  • What happens to fields deleted in the source stack during propagation?

    If a field is deleted in the source stack, the corresponding field and its associated data will be removed from the destination stack as well.

  • How does the automation determine whether to update or create a content type in the destination stack?

    The automation checks for the existence of the content type in the destination stack via an HTTP request. If it exists (HTTP 200), it updates; if not (HTTP 422), it creates the content type.

  • What headers are required for the HTTP actions in this automation?

    The required headers include api_key, authorization, content-type, and optionally include_branch, with credentials securely stored as project variables.