Marketing Architects icon

Marketing Architects

Consume Marketing Architects API
Join our community

Actions7

Overview

The node integrates with the Marketing Architects API to log events related to projects. Specifically, the "Log Event" operation under the "Project" resource allows users to send custom log messages associated with a particular project ID. This is useful for tracking significant occurrences or milestones within a project workflow, such as completion of image generations or other automated tasks.

Practical examples include:

  • Logging when a batch of images has been generated successfully.
  • Recording status updates or errors during project execution.
  • Tracking user actions or system events tied to a specific project.

This helps maintain an audit trail and facilitates monitoring and debugging in complex marketing automation workflows.

Properties

Name Meaning
Project ID The numeric identifier of the project to which the log event will be associated.
Message The textual message describing the event to log (e.g., "Image generations completed").
Retry Settings Configuration options for retrying the request on failure:
- Enable Retry on Failure Whether to retry sending the log if the initial attempt fails (true/false).
- Max Retry Attempts Maximum number of retry attempts allowed (1 to 10).
- Retry Delay (Seconds) Delay between retry attempts in seconds (1 to 60).
- Backoff Strategy Strategy for calculating delay between retries: either "Fixed" (constant delay) or "Exponential" (increasing delay).

Output

The node outputs JSON data representing the response from the Marketing Architects API after attempting to log the event. This typically includes confirmation of the logged event or error details if the request failed.

If the API supports binary data output for this operation, it is not indicated in the provided code or properties, so the output is expected to be purely JSON.

Dependencies

  • Requires an API key credential for authenticating with the Marketing Architects API.
  • The base URL for requests is https://pushbtn.api.misfitsandmachines.com.
  • The node sends POST requests to the /logs endpoint with the project ID and message in the request body.
  • The workflow name is automatically included as the source of the log event.

Troubleshooting

  • Common Issues:

    • Invalid or missing project ID may cause the API to reject the log event.
    • Network issues or API downtime can prevent successful logging.
    • Incorrect or expired API authentication token will result in authorization errors.

  • Error Messages:

    • Errors returned by the API are processed by a post-receive handler that surfaces them clearly.
    • If retries are enabled but still fail, ensure the retry settings are configured correctly and the API is reachable.
    • For authorization errors, verify the API key credential is valid and properly configured in n8n.

Links and References

Discussion