Automation Types in Fullpilot

Fullpilot supports different types of automations to accommodate various workflows and needs. This guide explains the structure and capabilities of automations within the platform.

Automation Structure

Every automation in Fullpilot consists of these key components:

1. Name and Description: Human-readable identifiers for the automation
2. Triggers: Conditions that initiate the automation
3. Steps: Sequential actions performed during execution
4. Integrations: Connected third-party services used within the automation

Trigger Types

Fullpilot supports four types of triggers that determine when your automation executes:

Manual Triggers

Manual triggers allow you to run an automation on-demand when needed.

Use when: You need to perform a process on-demand, often with different inputs each time.

Scheduled (Cron) Triggers

Scheduled triggers execute automations at specific times using cron expressions. You can set up recurring schedules with precise timing.

Use when: Your automation needs to run at regular intervals or specific times.

Integration Triggers

Integration triggers execute automations in response to events from connected third-party applications.

Use when: You need to respond to events happening in external services (like receiving an email, a form submission, or a calendar event).

Webhook Triggers

Webhook triggers create a unique URL endpoint that can receive data from external systems, triggering your automation when data is sent.

Use when: You need to integrate with systems that can send webhook notifications, or when native integration triggers aren't available.

Step Types

Automations can include different types of steps that perform various functions:

Generate-Text Steps

This is the default step type, using AI to generate content based on a prompt. Each generate-text step requires a model mode setting that determines the AI model's behavior:

• Fast Mode: Optimized for processing large amounts of text quickly and cost-effectively. Best for summarization, data extraction, or formatting tasks.
• Quality Mode: Provides sophisticated reasoning and creativity for complex tasks. Best for complex problem-solving, creative content, or detailed analysis.

Form Steps

Form steps collect user input during automation execution, enabling human-in-the-loop workflows.

Form fields can be of several types:

• Text: Single-line text input
• Textarea: Multi-line text input
• Number: Numerical input
• Select: Dropdown selection
• Checkbox: Boolean true/false selection
• File: File upload
• Image: Image upload

Working with App Functions

Automations can integrate with third-party services through app functions. These functions allow your automations to interact with external systems like Gmail, Slack, or Google Sheets directly within your workflow steps.

Attachments

You can include file attachments in your automations to provide reference materials or content for processing.

Best Practices

1. Choose the right trigger type for your use case - don't use a scheduled trigger when an integration trigger would be more precise

2. Select appropriate model modes for generate-text steps:

   • Use fast mode for summarization, extraction, and formatting
   • Use quality mode only for complex reasoning and creative tasks

3. Be specific in your instructions - clear directions lead to better results

4. Add form steps strategically - use them for genuine human decision points, not for configuration data

5. Use step dependencies effectively - reference outputs from previous steps when needed

6. Implement proper deduplication for scheduled and integration triggers to avoid processing the same items multiple times

By understanding the capabilities and structure of automations in Fullpilot, you can create more effective and efficient workflows for your specific needs.