This topic was automatically generated from Slack. You can find the original thread here.
Akash Joshi : Hey there! So we already have a zapier Integration. Do you have a developer dashboard where we can add our app or do you add them yourself for now?
Dylan Sather (Pipedream) : great question! Currently Pipedream employees add integrations, but anyone can develop event sources (triggers) and actions tied to those apps.
What kinds of triggers / actions do you have in Zapier? We operate a similar developer interface for developing those resources, so I’m interested in what you’d like to expose on Pipedream.
Akash Joshi : Hi . That is actually a great idea. We can get a bare minimum setup with all APIs on gitlab so anyone could try the full functionality with their account.
Pravin Savkar : Thanks ! Should the API key be used to get an access token on every API request (as modeled in this example), or should Pipedream “refresh” the token on a regular interval behind the scenes (similar to the process for refreshing OAuth tokens)?
Akash Joshi : I will have to confirm with the backend team but I believe the access tokens are valid for 30 days. You definitely do not need to create access token for every request. You have to use Step 1 only the first time to get a token from the API key and you can use the token for a month at least. I will get back to you with the exact validity
Pravin Savkar : Also, is your model for exchanging the API key for a token based on a standard or is that a proprietary flow? Do you support OAuth? I see two options that would unblock the integration quickly:
Configure an OAuth integration (if you support it). We will automatically refresh the token in the background so users can easily reference the token in code.
Set up Linkish as an API key integration (but that will require users to exchange the key for a token on every event).
Let me know if you have any other suggestions. If we have to develop a custom integration that will need to be prioritized against other items on our backlog.
Akash Joshi : You can do it the #2 way if that is easy for you. Create new access token on every event. Each access token is valid for 30 days ( I just confirmed it ).
Pravin Savkar : - I set up the Linkish app using the API key strategy. You can check out the app page in our marketplace at Linkish API Integrations - Pipedream. You’ll see a code snippet on that page with a shortcut to run it in a workflow (you can easily modify the code to hit any other endpoints as well).
I also recommend checking out our quickstart for source development as well as the component API reference. You can use that documentation to develop Linkish sources (we will be updating actions to use this same model in the near future). Let us know if you have any questions or feedback.
Akash Joshi : Hey . Thanks for putting this together. I saw that the code snippet wasn’t creating any links in the linkish dashboard. They were basically just pulling the collection list. I extended it so it would actually save something in the dashboard. Can you please add the snippet from below to the marketplace?
Pravin Savkar : we typically don’t modify resources with the sample code snippet – that behavior is typically reserved for actions. Do you have any concerns with that approach?
Akash Joshi : The only concern I had was that the what you shared did not create any link. It only pulled the list of collections from the database. If you think users will be able to find our docs and use the second API to actually create a link then its fine.