12-24-2019 20:11 PM - last edited 12-24-2019 20:40 PM
Let's take the challenge of creating our own Custom Connector with flow, in this first part of a two-part series that explores the core elements of Custom Connector Definitions. I am purposely using a very simple scenario, and tomorrow we'll go deeper.
1. There is a sight nuance to triggers....triggers can't be related to another API as I indicated in the example. Triggers are related to the Custom Connector being defined. In this case, something like when a new kitten photo is added.
2. Remember to pay attention to the query strings, this particular API was very simple so it didn't have a lot of parameters to think about. Set up your actions with the parameters that apply to the business, leveraging the different endpoints and parameters from the REST API (each will be different). If you're editing a custom connector, and you're finding it isn't acting as expected, recreate it from scratch and that will normally resolve the issue.
Learn more on custom connectors here:
Come back for part 2 (on day 25 of the 25 days of flow) of this topic:
Create your first custom connector