Create a new Sink in Twilio Events
A documented Twilio Events operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Create a new Sink
- POSTChanges data
events.twilio.com/v1/Sinks
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Twilio Events operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Twilio Events operations
- Create a new SubscriptionPOST · changes data
- Create a new Subscribed Event type for the subscriptionPOST · changes data
- Create a new Sink Test Event for the given SinkPOST · changes data
- Delete a specific SubscriptionDELETE · changes data
- Update a SubscriptionPOST · changes data
- Validate that a test event for a Sink was receivedPOST · changes data
- Remove an event type from a subscriptionDELETE · changes data
- Update an Event for a SubscriptionPOST · changes data
Questions
- Can HumDay create a new sink in Twilio Events?
- Yes. This operation is published in Twilio Events's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Twilio Events data?
- Yes — this is a POST operation, so it changes something in Twilio Events. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Twilio Events account.
Where this came from
Read from a published API description for Twilio Events at raw.githubusercontent.com/twilio/twilio-oai/main/spec/json/twilio_events_v1.json. The description above is the provider’s own wording, not ours. Last published 2023-04-20.