I am struggling to set up parser

Hire a Pro Hire Help
1

I am trying to send crypto signals to a webhook. I have my system receiving all the data I need but can’t figure out how to parse text and forward to a webhook. The easiest solution is to hire an expert.

1 Like
3

Hey, you can use the basic JavaScript Code node to parse the data.

Paste the incoming data into ChatGPT, and it will generate the parsing logic for you.

If you need deeper help, feel free to reach out at shashwatanandsingh2025@gmail.com.

4

Hello @cory_ransom , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications

5

Hi @cory_ransom,

If your system is already receiving the signal data, then this is likely a structuring issue before forwarding it to the webhook.

In Make, this can be handled using the Text Parser module with regex groups, or by extracting structured fields first and then mapping clean outputs into the webhook module. The key is defining consistent patterns in the incoming signal.

If you’re open to sharing a masked sample of the signal format, I can suggest the exact parsing logic.

If you prefer hands-on support, you can reach me directly:

Email: folafoluwaolaneye@gmail.com

Book a call: Discovery Call | Folafoluwa Olaneye | Cal.com(P.S: Adjust to your respective timezone )

Portfolio: View my past automation works here.

Best regards,

Folafoluwa Stephen

Flowedge Digitals

Make.com Automation Specialist

1 Like
6

Hi,

This sounds like a small repair rather than a big build. If the signal text is already arriving, then the job is to reliably extract the fields you need, normalize them, and forward the clean payload to the webhook without brittle string handling.

If you are still looking, this is the kind of same-day parser or webhook fix I would be comfortable taking on as a fixed-scope task.

7

Hi Cory,

I can help with this.

I work a lot with Make.com and webhook-based workflows, including parsing structured or unstructured text and forwarding the cleaned data to external endpoints.

From what you described, the solution usually involves:

1* Capturing the incoming signal text and identifying the key fields (pair, entry, stop loss, targets, etc.).

2* Parsing the message using a text parser or structured extraction so the data becomes usable fields instead of raw text.

3* Formatting the parsed data into JSON.

4* Sending the structured payload to your webhook using an HTTP request module.

Once the parsing logic is set up, the signals can flow automatically to your webhook every time a new one is received.

If you want, you can share an example of the signal text you’re receiving and the webhook format you need, and I can help you set it up quickly.

You can also reach me at:
fopefoluwaakinola@gmail.com

Happy to help you get this working.

8

Hi there,

I can get your signals flowing to your webhook today. Parsing unstructured signal text (like Telegram alerts or email alerts) and turning them into clean JSON payloads is exactly what I do.

Here is how I’ll solve your parsing bottleneck:

  • Signal Parsing: I’ll use Regex or OpenAI (if the signals are messy/varied) to extract the key data points: Ticker, Entry, SL, and TP.

  • Webhook Formatting: I’ll transform that data into the specific JSON format your target system requires.

  • Reliability: I’ll add a “Validation Step” so that if the text format changes or a signal is incomplete, the webhook won’t break—it will log an alert or skip the bad signal.

I’m comfortable working with n8n or Make.com and can handle high-frequency data without lag.

My Work: https://mikedevai.netlify.app/ Telegram: @hely_chatbots