See llms.txt for all machine-readable content.
Save yourself the work of writing custom integrations for Prospe AI and Redis and use n8n instead. Build adaptable and scalable Sales, workflows that work with your technology stack. All within a building experience you will love.

| Delete | |
|---|---|
| Get | |
| Head | |
| Options | |
| Patch | |
| Post | |
| Put |
To set up Prospe AI integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Prospe AI to query the data you need using the API endpoint URLs you provide.
See the example hereRequires additional credentials set up
Use n8n's HTTP Request node with a predefined or generic credential type to make custom API calls.
| Delete | Delete a key from Redis |
|---|---|
| Get | Get the value of a key from Redis |
| Increment | Atomically increments a key by 1. Creates the key if it does not exist. |
| Info | Returns generic information about the Redis instance |
| Keys | Returns all the keys matching a pattern |
| List Length | Returns the length of a list |
| Pop | Pop data from a redis list |
| Publish | Publish message to redis channel |
| Push | Push data to a redis list |
| Set | Set the value of a key in redis |
Discover our latest community's recommendations and join the discussions about Prospe AI and Redis integration.

Carlo
Hi, I’m stuck with a problem in my n8n workflow. I’m trying to retrieve all the messages stored in a Redis list (used by my chatbot), but with the Redis node i can only returns the last element of the list or SET. What…

