When working with Twilio Functions, you might need to create resources you'd like to store locally for one-off activities. For example, you might like to create a file with user-provided data and send it onto the next step in a flow based on your business needs.
In Functions, anything that you create on-the-fly gets stored in the
temporary folder, which may not be obvious at first.
In this quick tutorial, I'll show you how to access and utilize the temporary storage under Functions for your purposes. Let's get started.
Temporary Storage in a Twilio Function
If you try to perform operations anywhere other than the temporary folder in the underlying OS filesystem you will see something like:
Below I show a Twilio Function writing to and retrieving from the relevant temp folder:
/** * * This Function shows you how to reach and utilise the temporary storage under the …
When working with Twilio Autopilot, dealing with FAQs is not as straightforward as with typical user Intents and Tasks.
Let's get started.
Components and architecture of our FAQ integration
In our case, we use the following components to build an FAQ integration:
- Autopilot Tasks - to direct to the FAQ module. For example, we can make an “unresolved” case, which means Autopilot could not match an existing Intent to the user input (and we then try to see if the query corresponds to something in the FAQ)
- Twilio Function - to take the specific user input that was not matched to an intent and send it to the backend for analysis.
- Elasticsearch - to link the backend of …