Retrieving Data from a Record Created by an HTTP Request

Questions
1

Describe the problem/error/question

I have a workflow that I want to create using n8n and I’m getting there but I need help. I am stuck at the create user step/node. It works just fine, it creates a membership in the WordPress MemberPress plugin. But I need info from that user/membership to assign them to a subscription. It’s the User ID and the Member ID I require to create the subscription. Just trying to figure out if there’s a way to get the data from the create user step or if I need to add a note to query against WordPress to get those bits of info. I’m stumped.

Please share your workflow

Google_Sheet__MemberPressWP__ActiveCampaign-_n8n_2025-01-14_10-53-48
Google_Sheet__MemberPressWP__ActiveCampaign-_n8n_2025-01-14_10-53-482440×572 128 KB

ut returned by the last node

Information on your n8n setup

  • n8n version: latest, self-hosted
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hey @digisavvy

If the post request is not returning the id in the response then I guess you will need to make a GET request to query the member to get what you need.

I can find any clear docs on this but my best guess would be:


GET /wp-json/mp/v1/[email protected]

Or another search term.

1 Like
4

Thanks for the reply! I thought that might be it too. I have a request that when I send through command line returns a single record, which is the most recent one. When I use an HTTP node set with GET, it works but I see no output.

▶️ BHTC - IDEAFit Signups - n8n 2025-01-14 13-22-03
▶️ BHTC - IDEAFit Signups - n8n 2025-01-14 13-22-032224×2574 204 KB

5

Strange. I found some API docs for this and they suggest that when you create the member, the response should include the ID and all of the other details.

I don’t have access to the API to test it, but other things I would suggest are to play around with the response type in the response format at the bottom of the POST request and see if that changes anything. Also, try turning on the ‘Always Output Data’ option in the Settings tab of the post node and see if that changes anything.

1 Like