Pricing
Pay per usage
This integration transfers data from Apify Actors to a Postgres SQL database (with PGVector extension).
Pricing
Pay per usage
Rating
4.6
(5)
Developer
Apify
Actor stats
5
Bookmarked
16
Total users
0
Monthly active users
9 months ago
Last modified
Categories
Share
Connection string for the Postgres SQL database in the format postgresql://user:password@host:port/database
The name of the collection to use. NOTE: This is not the name of the table, but the name of the collection
Choose the embeddings provider to use for generating embeddings
Configure the parameters for the LangChain embedding class. Key points to consider:
Typically, you only need to specify the model name. For example, for OpenAI, set the model name as {"model": "text-embedding-3-small"}.
It's required to ensure that the vector size of your embeddings matches the size of embeddings in the database.
Here are examples of embedding models:
For more details about other parameters, refer to the LangChain documentation.
Value of the API KEY for the embeddings provider (if required).
For example for OpenAI it is OPENAI_API_KEY, for Cohere it is COHERE_API_KEY)
This array specifies the dataset fields to be selected and stored in the vector store. Only the fields listed here will be included in the vector store.
For instance, when using the Website Content Crawler, you might choose to include fields such as text, url, and metadata.title in the vector store.
[ "text"]A list of dataset fields which should be selected from the dataset and stored as metadata in the vector stores.
For example, when using the Website Content Crawler, you might want to store url in metadata. In this case, use metadataDatasetFields parameter as follows {"url": "url"}
This object allows you to store custom metadata for every item in the vector store.
For example, if you want to store the domain as metadata, use the metadataObject like this: {"domain": "apify.com"}.
Choose the update strategy for the integration. The update strategy determines how the integration updates the data in the database.
The available options are:
Add data (add):
Upsert data (upsert):
Update changed data based on deltas (deltaUpdates):
Select the strategy that best fits your use case.
This array contains fields that are used to uniquely identify dataset items, which helps to handle content changes across different runs.
For instance, in a web content crawling scenario, the url field could serve as a unique identifier for each item.
[ "url"]When set to true, this setting enables incremental updates for objects in the database by comparing the changes (deltas) between the crawled dataset items and the existing objects, uniquely identified by the datasetKeysToItemId field.
The integration will only add new objects and update those that have changed, reducing unnecessary updates. The datasetFields, metadataDatasetFields, and metadataObject fields are used to determine the changes.
This array contains fields that are used to uniquely identify dataset items, which helps to handle content changes across different runs.
For instance, in a web content crawling scenario, the url field could serve as a unique identifier for each item.
[ "url"]When set to true, delete objects from the database that have not been crawled for a specified period.
This setting allows the integration to manage the deletion of objects from the database that have not been crawled for a specified period. It is typically used in subsequent runs after the initial crawl.
When the value is greater than 0, the integration checks if objects have been seen within the last X days (determined by the expiration period). If the objects are expired, they are deleted from the database. The specific value for deletedExpiredObjectsDays depends on your use case and how frequently you crawl data.
For example, if you crawl data daily, you can set deletedExpiredObjectsDays to 7 days. If you crawl data weekly, you can set deletedExpiredObjectsDays to 30 days.
When set to true, the text will be divided into smaller chunks based on the settings provided below. Proper chunking helps optimize retrieval and ensures accurate and efficient responses.
Defines the maximum number of characters in each text chunk. Choosing the right size balances between detailed context and system performance. Optimal sizes ensure high relevancy and minimal response time.