We can even do something cool internally like "when I complete this step, the user needs to fill out this data" and we could route that to Inbox for action! Logo integrations will also be where we see apps that aren't available on hosted solutions, like GoProposal, VirtualCabinet etc.įinally, the icing on the cake will be our API. That way you can literally integrate the integration (!!!) into your workflow! An example would be something like "when I click this step, send this Typeform to the client" or "when I complete this step, send this data to GoProposal" etc. With logo integrations, we are thinking of going well beyond the norm! We think these should include things like branded widgets, insights and steps. To be clear though, our ability to publish depends on you! We need a critical mass of users to test the integrations before Zapier will allow us to publish them. We hope to have all our triggers and actions ready and published to Zapier by the end of Jan 2020.
Targeting Zapier gives us the widest range of integrations on day one including Xero, Quickbooks, Toggl and Practice Ignition. We plan to target Hosted integrations first, starting with Zapier. Logo - this is where we do custom integrations with specific apps.Hosted - this is where we allow other apps to exchange data with us by using a platform that is owned by someone else e.g.API - this is where we allow other apps to exchange data with us by using a platform that we own.We see that there are 3 types of integrations: This means other apps can do these things on your data in onkho: We're planning to support the following actions. This means that other apps will know when these things happen and take some action on their own data. We're planning to support the following triggers. This time, we want to outline how we are going to deliver integrations.Īn integration is basically "when this happens (a trigger) in app 1, then do this (an action) on app 2".
Previously, we've discussed our approach - see the connected topic. It does not store any personal data.So, we are finally ready to look at integrations. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly.
0 kommentar(er)
