How to automate Wix blog posting via Make? Stuck on API "memberId" error

Questions
1

:bullseye: What is your goal?

Automate blog posting on my Wix website using Make.com. Content gets prepared in Make, then should be published as a blog post automatically.

:thinking: What is the problem & what have you tried?

There’s no native Wix blog module in Make, so I’m using the HTTP module to call Wix’s REST API directly (POST /blog/v3/draft-posts) with an API key + site ID. I successfully fetched my site’s member list via GET /members/v1/members.

The draft-posts call requires a memberId field. I’ve tried both the member’s “id” and “contactId” from the members list — both get rejected as “does not exist”. My only site member is my own owner account, showing status: UNKNOWN.

Has anyone gotten this working? Specifically — where did your memberId come from, and does the account need to be an active Members Area member (not just the site owner/dashboard user)? Any working example would help a lot. Thanks!

:clipboard: Error messages or input/output bundles

{“message”:“INVALID_ARGUMENT: Invalid request body memberIds:[] do not exist”,“details”:{“applicationError”:{“code”:“INVALID_REQUEST_DATA”}}}

3

the status: UNKNOWN on your member is the actual tell here, that’s why the id keeps getting rejected.

wix treats your account owner and a site member as two different things. the owner isn’t automatically a site member, so what you’re pulling back from /members/v1/members is a half provisioned record, and the draft-posts endpoint won’t accept an id that doesn’t resolve to a real active member. contactId won’t work either, that’s the CRM contact id, a completely different id space from the member id blog wants.

what i’d do is create a proper site member first, either sign up on your own site as a member with a real email, or create one through the members api, then approve it so status comes back ACTIVE instead of UNKNOWN. pull the members list again, grab the id off that active record, and use that as memberId. that’s usually where the draft-posts call starts going through.

worth checking your api key has blog permissions too, but the unknown status is almost certainly your blocker, not the key.