How can I include metafieldNamespaces in the Webhook settings in app.toml?

I want to migrate the registration of an existing service’s webhook to TOML format, but I don’t know how to migrate `metafieldNamespaces`.

There was no mention of metafieldNamespaces in these documents.

Hey @Shota_Yamamoto :waving_hand: - happy to take a look into this, just to clarify, which webhook subscription topic were you looking to migrate over to the defined webhooks in your app’s .toml?

Was it META_OBJECTS_UPDATE, for example? How had you set up the webhook subscription initially? Hope to hear from you soon, let me know if I can clarify anything here on my end.

    ORDERS_UPDATED: {
      deliveryMethod: DeliveryMethod.PubSub,
      pubSubProject: process.env.GOOGLE_CLOUD_PROJECT ?? "",
      pubSubTopic: "yyyyyy",
      metafieldNamespaces: ["xxxx"],
      includeFields: [
        "id",
        "admin_graphql_api_id",
        "app_id",
        "location_id",
        "line_items",
        "shipping_lines",
        "discount_applications",
        "refunds",
        "fulfillments",
        "updated_at",
        "cancelled_at",
        "processed_at",
        "name",
        "customer",
        "currency",
        "billing_address",
        "shipping_address",
        "payment_gateway_names",
        "tax_lines",
        "tags",
        "note",
        "taxes_included",
        "financial_status",
        "total_price_set",
        "created_at",
        "updated_at",
        "note_attributes",
        "metafields",
        "source_identifier",
      ],
    },

This is my webhook.

This is not yet supported :pensive_face:

Oh, So sad. Will all Metafields be included in the Payload?

No, you won’t be able to get metafields at all if you switch to webhooks defined in app toml file

OK! Thanks, I have 5 webhook topics. Do you know if it’s possible to migrate only those that do not require a metafield?

Yes, you can do that. Don’t forget to delete them once you migrate them to toml

1 Like