• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -
     

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

„Klick-Tipp : Add Contact“ gets „Error 32“

When I use the action „Klick-Tipp : Add Contact“ I always get the „Error 32“

How can I solve this?

Name of my Workflow:
220503 Frank Kern Mentortools - Lead
 

Attachments

  • Pabbly_Connect.jpg
    Pabbly_Connect.jpg
    60 KB · Views: 43

Supreme

Well-known member
Staff member
Hey @Peter Martini

As we can see from your workflow you haven't mapped correctly decoded email address from the "Facebook Lead Ads: New Lead (Instant)".

Though we have mapped the email address correctly. Kindly give it a try and let us know how it works for you.

2022-05-06_17h35_38.png



2022-05-06_17h38_34.png
 
Thank you for your fast answer, Supreme

But this is not the problem. The email address is correctly mapped.

The mistake comes from the Trigger „Facebook Lead Ads : New Lead (Instant)“

The Trigger delivers wrong data: „Res1 Res1 Res4 Email“

Correct would be: „Res4 Email“

The mistake startet on May 04, 16:57:11
1.jpg


It comes from the Trigger „Facebook Lead Ads : New Lead (Instant)“:
2.jpg


The Trigger delivers wrong data: „Res1 Res1 Res4 Email“
3.jpg


Wrong E-Mail:
4.jpg


Correct E-Mail from former Workflow:
5.jpg
 
It was a mistake of their new trigger event "New Lead (Instant)" which was at that time in beta

Back then I switched to the old trigger event "New Lead" and it worked.

Today the mistake has gone. Both are working.
 
Top