Iniciar sesión
Iniciar sesión
Idloom is happy to announce its compatibility with Zapier, allowing you to connect your favorite event management software to over 1,000+ third party apps.
Need to integrate your event guest list into your favorite CRM? To send emails to your registrants via your own mailing software? To generate invoices with your specific invoicing tool…?
The new idloom-Zapier integration lets you do all that and much more, in just a few clicks ! Stick with the tools that work for you, and let them work seamlessly with idloom-events.
Zapier integration is now available to all idloom-events customers, starting from the Light subscription plan. No set up required, connect idloom-events seamlessly to your Zapier account, and let it work for you. More information at www.zapier.com.
Feel free to reach out to us at info@idloom.com for any assistance or additional informations,
Good luck with your future events!
The idloom-events Team
Zapier integration FAQ
idloom-events may return errors to Zapier in some specific cases and Zapier returns them to you. Read them attentively, they are usually self-explanatory.
Errors and workaround:
- “Error: no guest available for that account”: To create your zap and activate it, Zapier needs to receive a sample data set. To do so, idloom-events returns the last guest who registered to your events. This message means that you don’t have any yet.
Workaround: just register yourself to any of your events and try again. - “Error: Unknown API key or API access not allowed. Check your settings.”: The API you entered does not exists in this account or you didn't allow API access.
Workaround: Check both your API key and account name in your Zapier and/or idloom-events settings, and that the Allow API access check-box is checked and try again. - “Error: account not found. Check your Account name.”: The account name you entered does not exists.
Workaround: Check both your API key and account name in your Zapier and/or idloom-events settings and try again. - “Error: bad request”: the requests received by idloom-events is malformed. Contact idloom-events support team for further details and how to solve this.
You may also encounter issues while activating your zap or registering new ones.
Zapier returns the error message from idloom-events. Read them attentively, they are usually self-explanatory.
Errors and workaround:
- "Error: zap already exists for that profile. Delete it first.": You already have a zap registered for this action and profile. We only send the information once to Zapier. You can then create as many actions as you want in your zap.
Workaround: If you want to register a new zap for a given profile / action, you first have to switch off the existing one. - “Error: Unknown API key or API access not allowed. Check your settings.”: The API you entered does not exists in this account or you didn't allow API access.
Workaround: Check both your API key and account name in your Zapier and/or idloom-events settings, and that the Allow API access check-box is checked and try again. - “Error: account not found. Check your Account name.”: The account name you entered does not exists.
Workaround: Check both your API key and account name in your Zapier and/or idloom-events settings and try again. - “Error: bad request”: the requests received by idloom-events is malformed. Contact idloom-events support team for further details and how to solve this.
Yes, you must check the box allowing access to the APIs of your account / profile to allow Zapier to connect and configure the zaps.
Do not forget to check the automatic sending of registrations to zaps, otherwise the sending of real-time information will not be done.
Once these are configured, you can then disable API access for more security, the zaps will continue to work normally.
Related articles
Your custom application integration with idloom.events
Didn't find the app you would like to connect idloom.events to?
API field mapping feature
In addition to its full set of API methods, idloom-events allows you to define a subset of data to be sent, translate the fields naming and define fixed values before sending it to your remote system.