Is It Permissible to Create a Non-Service/API-Related Component for Bayes Classification of Banking Transactions?

1

This topic was automatically generated from Slack. You can find the original thread here.

Hello,
I want to implement a Bayes Classification for banking transactions based on the transaction description.

I can use the bayes-classification lib or the natural lib to do it but since this component could interest many more people, I was wondering :

Is it allowed to create a component which is not related to any online service/API?

In my case, it would be a Bayes Classification component with the following actions:

• Create
• Train
• Classify
Thank you

2

Hi Lucas, great question. where do you think this component should live?

3

For context, we’ve have historically similar requests but using Python code (see #5844 and #6951 ).

we don’t have a way of integrating the Python package natively onto our marketplace today. We can support apps via REST API or Node.js the way you are envisioning.
He is correct @Dnartskel , the integrations for Pipedream refer to actual 3rd party services.
Whereas the support you’re looking for is a Python library.
I recommend learning Python in more detail first, which is the foundation you’ll need to leverage Pipedream or any other system that uses this gpt-index PyPI package.
Once again, PyPI packages are installable pieces of software. So you can import gpt-index as a package within a Pipedream Python code step, but there is not gpt-index service a.k.a. “app” that Pipedream needs to integrate with.
but node.js is technically possible.

4

It would be a component without API. So can I do it?

5

is our PM for Integrations and I’d like to get his advice on this. We’ve provided abstract groups of “appless” components like this, e.g. Helper Functions. It may make sense for us to create a “Statistics” category or something similar here

6

whatever grouping we decide on, you’d be able to attach the app prop to the component like you normally would. But we’d specify that there’s no account required, so adding the app prop to the component would only help to put it in the right group (users wouldn’t see any connect account buttons in the UI like for normal apps)

7

Hi Lucas, let me think about this for a little bit and get back to you on the best place for this to live.

8

Another library that has been constatly brought app without much detail (not much elaborated like Lucas’) is STATA, or rather STATA related Python libraries

9

It is not that complicated actually. I plan to do only one action:

Props:
• Object representing the trained data
• String (to classify)
https://github.com/miguelmota/bayes-classifier

10

Thanks for the detail. I meant to say that users who have requested STATA don’t fill the details you see when you create a new GitHub Issue in the Pipedream repo

11

Mmm ok. Won’t be my case (I hope). I’ll try with a custom node action first anyway

12

I’m having bad results. Will be more complicated than planed…