• 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

Recent content by Finding Frodo

  1. F

    Data Forwarder → Return Data to Source → Within a Router

    @Supreme …which would mean to double or even triple all ~20 following actions of the outer workflow into 2-3 cases of the router. Would be much easier if we had a single IF-Action as suggested above. Or if it would be possible to add more steps after a router.
  2. F

    Data Forwarder → Return Data to Source → Within a Router

    @Supreme Okay, so what exactly is the current (inner) workflow's source? Isn't that the caller of the webhook? Is there any other way in Pabbly, to create a workflow that behaves like a web service? → getting called by url with params, returning JSON data when done How else can I achieve what...
  3. F

    Data Forwarder → Return Data to Source → Within a Router

    @Supreme Thank's for clearification :) I tried my best with this video:
  4. F

    Data Forwarder → Return Data to Source → Within a Router

    It's step #7 in the outer workflow, that uses the Data Forwarder. Anyway, the call works perfectly. It's the return that does never happen. Data is returned in the inner workflow in each router condition: Is it maybe a syntax problem of the returned JSON Data?
  5. F

    Data Forwarder → Return Data to Source → Within a Router

    Hi there, here is what I'm basically trying to achieve: Outer workflow Calling inner workflow via Pabbly Data Forwarder: Forward Custom Data Inner workflow: receiving data doing stuff using a Pabbly Router Route 1: returning data to outer workflow via Pabbly Data Forwarder: Return Custom...
  6. F

    Pabbly ↔ Klick-Tipp / 500 Proxy Error / SSL Handshake Problem

    It seems that there were some server issues on Klick-Tipp's side. This is fixed now and pabbly workflows run as expected.
  7. F

    Pabbly ↔ Klick-Tipp / 500 Proxy Error / SSL Handshake Problem

    Hi support, since 2 days I receive this result on my Klick-Tipp connection: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n<html><head>\n<title>500 Proxy Error</title>\n</head><body>\n<h1>Proxy Error</h1>\nThe proxy server could not handle the request<p>Reason: <strong>Error during SSL...
  8. F

    Pipedrive issue since latest API changes

    Alright, this now really seems to work. Find or Create Person Delay 1 minute Find Person Find of Create Deal Delay 1 minute Find Deal ... do other stuff with returned IDs from #3 and #6
  9. F

    Pipedrive issue since latest API changes

    @Supreme Yes, that's clear. But the person exists for 100% sure, because I executed Find or Create Person in the step before. So in the next step, Find Person, there is a 100% chance to find at least 1 result item. So there must always be a [Data Items 0 Item ID]! Could this be a timing...
  10. F

    Pipedrive issue since latest API changes

    @Supreme Okay, so I guess that's the only way. But can you explain why this is necessary? Because since I now use Find Person in any case and this returns the Person ID in the same Res structure, no matter if the person was created or found in the step before, it seems not very logical.
  11. F

    Pipedrive issue since latest API changes

    @Supreme The workflow is still https://connect.pabbly.com/workflow/mapping/IjU3NjEwNTZjMDYzZjA0MzM1MjY1NTUzNyI_3D_pc – "Buch Kauf an Klick-Tipp und Pipedrive senden" But there is no router. It's just a different set of follow-up actions, that should work much easier.
  12. F

    Pipedrive issue since latest API changes

    @Supreme But there is still something strange right now. Update Person and Update Deal, now #14 and #15 in the workflow (see history IjU3NjcwNTZlMDYzNDA0MzE1MjY0NTUzMDUxMzQ1MTY0NTQzNiI_3D_pc) still throw the "missing ID" error, though I definitely pass the existing IDs along. What's wrong there? 😳
  13. F

    Pipedrive issue since latest API changes

    That didn't work either. Text Formatter / Default Value also seems to forget data points, when they are no longer available. Now I do this: Find or Create Person Find Person Find of Create Deal Find Deal So in step 2 and 4 it finds a Person / Deal in any case and returns its ID in the same...
  14. F

    Pipedrive issue since latest API changes

    Doesn't work, it loses the connection to one of the values, as soon as the result is caught again to get the second value. Also the next API function throw an error, "unknown API function". Here is a workaround, that does the job for the moment: I use a Pabbly / Text / Default Value Action to...
  15. F

    Pipedrive issue since latest API changes

    Well yes, this is exactly where I came from. It is very cumbersome. Find or Create Person / Deal should be the solution to make such complexity obsolete. So would it be a solution, to put the resulting IDs from both Res into the next step's parameter? → [Res1:ID][Res2:ID] If only one of both...
See more
Top