Search Person Entities. Can perform more complex filtering based on the query defined in the request body.
Request body which must comply to the following JSON Schema:
{ "required" : [ "field_ids", "query" ], "type" : "object", "properties" : { "field_ids" : { "type" : "array", "description" : "Fields to include as columns in the search result entities - array of field_id strings", "items" : { "type" : "string" } }, "query" : { "type" : "array", "description" : "Search query to perform on the designated entity", "items" : { "required" : [ "field_id", "operator_id", "type" ], "type" : "object", "properties" : { "type" : { "required" : [ "predicate" ], "type" : "string", "description" : "The type of query", "enum" : [ "predicate" ] }, "field_id" : { "type" : "string", "description" : "The field to operate on" }, "operator_id" : { "type" : "string", "description" : "Description of operators:\n * blank - Blank\n * eq - Equal\n * not_eq - Not equal\n * gt - Greater than\n * gte - Greater than or equal\n * lt - Less than\n * lte - Less than or equal\n * starts - Starts\n * contains - Contains\n * between - Between\n * includes - Includes\n * not_includes - Does not include\n * includes_all - Includes all\n * not_includes_all - Does not include all\n * domain_eq - Domain equals\n * domain_blank - Domain is blank\n", "enum" : [ "blank", "eq", "not_eq", "gt", "gte", "lt", "lte", "starts", "contains", "between", "includes", "not_includes", "includes_all", "not_includes_all", "domain_eq", "domain_blank" ] }, "values" : { "type" : "array", "description" : "values array with data type matching field_id type", "items" : { "type" : "object" } } }, "description" : "A simple search criterion" } }, "order" : { "type" : "array", "description" : "Order in which the search results should be returned", "items" : { "required" : [ "field_id", "sort" ], "type" : "object", "properties" : { "field_id" : { "type" : "string", "description" : "Name of the field to sort on" }, "sort" : { "type" : "string", "description" : "Direction of sorting", "default" : "asc", "enum" : [ "asc", "desc" ] }, "nulls" : { "type" : "string", "description" : "Whether to include null values at the beginning or end of the sort. Defaults to end.", "default" : "last", "enum" : [ "first", "last" ] } } } }, "limit" : { "type" : "integer", "description" : "Number of rows to return. Default is 100, min is 1, max is 2000." }, "before_id" : { "type" : "string", "description" : "Used to paginate search results to the previous page. before_id should be the uuid of the first item in the current page. May not be provided simultaneously with after_id.", "format" : "uuid" }, "after_id" : { "type" : "string", "description" : "Used to paginate search results to the next page. after_id should be the uuid of the last item in the current page. May not be provided simultaneously with before_id.", "format" : "uuid" } } }
Specify how the response should be mapped to the table output. The following formats are available:
Structured Table: Returns a parsed table with data split into rows and columns.
Field Type: enum
Searchable: Yes
Search Operators: blank, eq, includes, not_eq, not_includes
Possible values are:
A Person's gender
Field Type: enum
Searchable: Yes
Search Operators: blank, eq, includes, not_eq, not_includes
Possible values are:
This is the auto-generated layout for the profile
Field Type: enum
Searchable: Yes
Search Operators: blank, eq, includes, not_eq, not_includes
Possible values are:
Override the layout of the Entity Profile
Field Type: enum
Searchable: Yes
Search Operators: blank, eq, includes, not_eq, not_includes
Possible values are:
Raw Response: Returns the raw response in a single row with the following columns:
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension Crunchbase Nodes from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.