Starts the workflow on SendGrid Event Webhook events
Usage and specifics
Publish the workflow, then configure the provider webhook with the displayed URL. autoSetup attempts automatic configuration according to provider support and permissions. A test payload simulates an event without proving actual delivery.
Technical type : sendgrid_trigger. Runtime : nodulz.
Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Parameter
Type
Default
Values / limits
rateLimitEnabled
boolean
-
-
rateLimitMax
number
-
-; > 0
rateLimitWindowMs
number
-
-; > 0
allowedIps
array
-
-; max 256
blockedIps
array
-
-; max 256
credentialId
string
""
-
events
array
[]
-
secret
string
-
-
webhookPath
string
""
-
autoSetup
boolean
true
-
mailgunDomain
string
""
-
snsTopicArn
string
""
-
configurationSetName
string
""
-
rules
object
-
-
rules.emailContains
string
""
-
testPayload
string
""
-
webhookId
union
-
-
subscriptionArn
string
-
-
setupError
string
-
-
lastError
string
-
-
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
Starts the workflow on SendGrid Event Webhook events
Usage and specifics
Publish the workflow, then configure the provider webhook with the displayed URL. autoSetup attempts automatic configuration according to provider support and permissions. A test payload simulates an event without proving actual delivery.
Technical type :
sendgrid_trigger. Runtime :nodulz.Credentials and prerequisites
Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
rateLimitEnabledbooleanrateLimitMaxnumberrateLimitWindowMsnumberallowedIpsarrayblockedIpsarraycredentialIdstring""eventsarray[]secretstringwebhookPathstring""autoSetupbooleantruemailgunDomainstring""snsTopicArnstring""configurationSetNamestring""rulesobjectrules.emailContainsstring""testPayloadstring""webhookIdunionsubscriptionArnstringsetupErrorstringlastErrorstringInitial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "credentialId": "", "events": [], "autoSetup": true, "webhookPath": "", "testPayload": "" }Verification
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
See also : Expressions and data, Executions, Node catalog.