Actions33
- Campaign Actions
- Contact Actions
- Field Actions
- Opt-In Actions
- Opt-in-Case Actions
- Sign in Form Actions
- Storage-Field Actions
- Tag Actions
Overview
The node integrates with the 4leads platform, allowing users to manage various resources such as campaigns, contacts, tags, opt-ins, sign-in forms, and more. Specifically, for the Sign in Form resource with the Stop operation, the node stops or deactivates a sign-in form process associated with a particular contact.
This functionality is useful in scenarios where you want to programmatically halt a sign-in form session or interaction for a user/contact, for example:
- Canceling an ongoing sign-in process if the user no longer wishes to proceed.
- Managing user sessions dynamically based on external triggers or business logic.
- Automating workflows that require stopping sign-in forms under certain conditions.
Properties
| Name | Meaning |
|---|---|
| Sign in Form | Select the sign-in form to stop. You can choose from a list of available sign-in forms or specify the ID directly. |
| Contact | Select the contact associated with the sign-in form session to stop. Can be chosen from a list or specified by ID. |
Additional note property (informational):
- The email of a contact can be used as an alternative identifier when selecting the contact.
Output
The node outputs a JSON array containing the results of the stop operation on the sign-in form. Each item in the output corresponds to the response from the 4leads API after attempting to stop the sign-in form for the specified contact.
If the operation returns multiple results, they are flattened into a single array.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the 4leads platform.
- Relies on the 4leads API endpoints related to sign-in forms and contacts.
- The node uses internal handlers (
signInFormHandler) to perform the stop operation.
Troubleshooting
- Invalid Sign in Form ID: If the provided sign-in form ID does not match the expected numeric format, the node will reject it due to regex validation. Ensure the ID consists only of digits.
- Contact Not Found: Selecting a contact that does not exist or is not linked properly may cause errors. Verify the contact exists in 4leads.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from executing successfully. Confirm the API key is correctly configured.
- Network or API Issues: Temporary network failures or 4leads service downtime can cause execution errors. Retry after some time or check service status.
Links and References
- 4leads Official Website — For general platform information.
- 4leads API Documentation (not publicly linked here) — Consult your 4leads account or support for detailed API docs related to sign-in forms and contacts.