Module Actions
Optionally, you can define the module's action to take advantages of features, read more below.
Last updated
Optionally, you can define the module's action to take advantages of features, read more below.
Last updated
© 2025 make.com
Used for modules that are creating an object, most of the time, these modules use POST request.
Module: Create a Contact
There are two types of responsiveness - synchronous and asynchronous. Read more about it in .
Used for modules that are retrieving an object, most of the time, these modules use GET request.
Module: Get a Contact
There is a difference between List/Search and Get modules although they use the same method "GET".
List/Search modules return multiple bundles and should be Module type: Search.
Get modules return only 1 bundle (specified by the entered ID) and should be Module type: Action.
If you happen to receive this error: Invalid module output. Expected Object, but found Array.
, it means that your module should be type Search. Type search expects an output type array, and unlike the type action supports pagination directive.
If you don't want to iterate the array returned from the API, you can wrap it in an object:
Used for modules that are updating an object, most of the time, these modules use PATCH or PUT request.
When a module is type Update, a new keyword appears inside Make - erase.
Module: Update a Contact
Used for modules that are deleting an object, most of the time, these modules use DELETE request.
Module: Delete a Contact
There are two types of update approaches - partial and full. Read more about it in .