Requests on multiple objects with same attribute


I would make a request on multiple different objects with the same attribute.

For example, I would like to make a task who can accept a Person, a Linkedin Account, a Google+ account and more object with a credential attribute, and link the result according to the begin object.

Do you have a tips or a guideline to do it ?

Thank you.


Hello! We apologize for a late reply.
Do you want to specify several social network accounts (or credentials) as input data and search for related email or phone numbers by linking this data on the diagram? If so, then, unfortunately, currently it is not possible to get an e-mail or phone number for a social network account or credentials. We plan to provide requests for those cases when users specified email explicitly on the page.
If not explicitly indicated, the data will not be obtained.
In other words: you can get information on accounts by mail or phone and link them to the diagram. You need to specify the email or phone as input data, and then search for the necessary sources. Further, all requests can be displayed in one general diagram.
You can do the reverse operation only if the email or phone number is available and open. We plan to add such requests.


I think you misunderstood my question.
Let’s take a schema, on which I have 3 objects: LinkedIn Account, Telegram Account and Person.
All 3 have a “credentials” property that interests me.
So I have a task that takes this property in input.

I would have liked to know if there was a way to have a single task that takes the “credentials” property in input but which on the output, on the schema, is able to link my output object to the input object (LinkedIn, Telegram, Person,…) that corresponds to it automatically.

We can imagine a case where a “credentials task” can be used to link automatically various “people object” to organisation object.

Do I have to do one task per object, even if they are exactly the same.

I hope I’m more clear.


Unfortunately, it’s not possible to automatically link your new object to the existing object on graph, because value source for your input is an attribute, and attribute is an independent entity without any knowledge about what graph object or link has it.
To link your custom object to the existing one, your task’s schema must have an object of requested type with filled identifiyng attribute and a link to your object.
For example, to link your object, say, ‘MyObj’, to LinkedIn Account on a graph, your schema should have a link (MyObj) -> (LinkedIn Account) and a value of LinkedIn Account’s identifiyng attrubite (URL) should be the same as existing one’s. That applies to each object type you want to connect to, but you don’t need one task per object, you can place them all on one schema or create multiple schemas and even separate header for each object type, each with own schema.

Custom tasks can’t connect existing objects to anything, they only able to create new objects, which are merged with existing ones if their identifying attributes are the same. See