IF Then Step This step enables you to execute actions if a specific condition is true or false. If Then configuration As you can see in the following screenshot, the action is executed only if a moosend subscriber type value is equal to 1. Similarly, you can add any number of actions to this branch… Continue reading If Then
Month: January 2021
Trigger Conditions
Trigger Conditions Trigger conditions enable you to filter trigger events based on the payload that is produced. For example, you can filter a QuickBooks event to only process invoices if the criteria meet a specific country, customer, or amount, etc. In the below example workflow is triggered only if a Salesforce contact is created… Continue reading Trigger Conditions
Realtime
Real-time triggers Real-time triggers are usually built on top of an asynchronous notification mechanism. Real-time triggers typically require registration in your connected app to let the app know that you are looking for a specific event. When that event occurs, the app will send a notification to APIFuse and generate a trigger event. Webhooks are… Continue reading Realtime
Action
Steps: Workflow steps can be actions, or control flow statements that help you describe business logic. Action step Actions carry out an operation in your target application (usually a create, update, or search operation). Each action requires a set of input fields and depending on the operation it may return output data Example Action: Insert… Continue reading Action
Polling
Polling triggers Polling triggers periodically check for new events by querying the app to see if new events are available. The polling frequency is configured in the Monetization plan section of API Fuse. The lowest polling frequency is 5 minutes.
Configuring a Trigger
Triggers Triggers determine what event to listen to in order to execute the actions described in a workflow. Trigger events can be configured based on apps (e.g. Salesforce, Google Sheets, MySQL) when a certain event occurs (e.g. a new customer is created). Depending on the available API, APIFuse can receive trigger events in real-time, or… Continue reading Configuring a Trigger
User Authentication
User authentication To access the marketplace, home pages or listing pages, user authentication is not required. However, user authentication is required if the user wants to install the integration based on the workflow that has been configured that powers the integration. To authenticate the end customer with APIFuse you need to send a JWT token… Continue reading User Authentication
Embedding Marketplace
Embedding – Marketplace The APIFuse marketplace can be embedded inside the UI of your SaaS platform, as a white-labeled “Marketplace/App ecosystem” to match your brand. Your marketplace home page URL can be constructed as: https://<subdomain>.apifuse.io The Subdomain can be found in the embed -> settings section. <iframe frame-border=”0″ title=”app ecosystem” src=”https://<subdomain>.apifuse.io” height=”1000px” width=”1500px”></iframe> To only… Continue reading Embedding Marketplace
Listing Setup
A listing is an integration you want to expose within the marketplace to your end-users. This landing page is completely configurable to match your brand’s identity. This is where you will upload your integration content to explain the value of what the integration with your SaaS application and another application provides to your customers. Navigate… Continue reading Listing Setup
Marketplace Setup
The API Fuse Marketplace can be customized to match your SaaS products brand identity by allowing you to customize fonts, colors, logos, etc. Follow the below instruction to customize the integration marketplace. Login to APIFuse and navigate to the embed section. The embed page has three sections called Customize, Listings, and Settings. Customize – The… Continue reading Marketplace Setup