#Sergio Sánchez
vital drift
stoic cypress
Hi! Let me help you with this.
long tree
🙌
stoic cypress
Are you looking to know when the platform calls POST /accounts, or when the Connected account has finished onboarding?
stoic cypress
Please, give me a moment, I am checking.
I just checked, and there's no webhook events for this.
long tree
give some minutes
stoic cypress
The reason is that the request is made by you, synchronously, so your app already knows that the account was created.
long tree
I am thinking about and alternative rthat I want to share with you
stoic cypress
Hey @long tree is there anything else you wanted to share?
long tree
Hey @stoic cypress sorry I was in a call ... let me share with you a bit of context and maybe you have another alternative
I am doing a kind of integration between customer.io (to send email) and Stripe, and what I am doing is in a workflow:
1- Create an account
2- Generate the account-link using the account id
but the issue is that when I create the account, I have a timeout issue as customer.io only waits 4 seconds (it seems that stripe takes more time for the account creation)
so my ideas was: ok let me first create the account, and once the account is created (reason why I was looking for a webhook), I will generate the account_link to be shared with the user
but as we dont have this webhook.... do you know if I have another alternative?
for instance, could we create the account and generate the link in the same call ? is there any way to avoid this timeout issue?
vale zephyr
I don't understand, you don't need a timeout or a webhook. You call the API, it synchronously returns on the HTTP response the Account object, which has the details of the account including the ID, which you can save at that point
long tree
the issue is that customer.io has a limit of 4 sec before saying "timeout, response was not received on time", and even that the account creation is sync, it is taking more than 4 seconds so we dont have the details about the account
vale zephyr
yep creating the account can be slow
that seems like a limitation of your no-code platform really, wouldn't be a problem if you were writing the code yourself. There's no account.created event at least
long tree
yes it seems a limitation there 🤔 ok I will try to figure out how I can resolve it using another approach maybe using "Get accounts" endpoint after creating the account in order to get the data directly ffrom the API instead of waiting for the response