-
Instructions to Ask a Question
For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.
We offer seven comprehensive applications designed to help you efficiently manage and grow your business:
- Pabbly Connect
- Pabbly Subscription Billing
- Pabbly Email Marketing
- Pabbly Form Builder
- Pabbly Email Verification
- Pabbly Hook
- Pabbly Chatflow
Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.
🚀 Exclusive Lifetime Offers 🚀
We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:
- 🔥 Pabbly Connect — Lifetime Access for $249 — View Offer
- 🔥 Pabbly Subscription Billing — Lifetime Access for $249 — View Offer
- 🔥 Pabbly Chatflow — Lifetime Access for $249 — View Offer
Make a one-time investment and enjoy the advantages of robust business management tools for years to come.
-
API by pabbly giving error
- Thread starter Nico
- Start date
Nico
Member
URL: https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZmMDYzMzA0M2Q1MjY1NTUzMDUxMzci_pc
The error occurs in the second step.
Thank you!
Task History ID - IjU3NjUwNTY5MDYzNjA0MzM1MjY4NTUzNTUxMzc1MTZhNTQzNDBmMzEi_pc
Based on your Task History ID, we can see that the 'ID' field was not received in your trigger step. As a result, nothing was mapped to step 3 of the workflow, which led to the error you encountered.
Task History ID - IjU3NjUwNTY5MDYzNjA0MzM1MjY4NTUzNTUxM2E1MTY3NTQzNzBmMzci_pc
In your latest Task History ID, you did receive the 'ID' in the trigger step, and therefore did not encounter any errors.
Based on your Task History ID, we can see that the 'ID' field was not received in your trigger step. As a result, nothing was mapped to step 3 of the workflow, which led to the error you encountered.
Task History ID - IjU3NjUwNTY5MDYzNjA0MzM1MjY4NTUzNTUxM2E1MTY3NTQzNzBmMzci_pc
In your latest Task History ID, you did receive the 'ID' in the trigger step, and therefore did not encounter any errors.
Similar threads
