Connect Omie ERP with Asaas
Unlock the superpowers of Omie ERP + Asaas and automate your tasks without having to write a single line of code.
Omie ERP and Asaas
your way
Check out the available triggers and actions in the automation of apps Omie ERP + Asaas
Created customer or supplier
When a customer/supplier is created on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created customer or supplier
When a customer/supplier is created on Omie ERPTrigger
Customer code - generated by Omie
Integration code
Customer's full name/deal name
CNPJ / CPF of the customer
Customer's trade name
Telephone (DDD)
Telephone number)
Contact name
Address: Public place
Address: Number
Address neighborhood
Full address
Address: State
Address: City
Address: Zip Code
Address: Country Code
Telephone 2 (DDD)
Telephone 2 (number)
Fax (DDD)
Fax (number)
WebSite
State registration
Municipal registration
Suframa Registration
Applicant for Simples Nacional
Activity Type
CNAE Code - Tax
Rural Producer
Taxpayer
Internal Observation
Customer or Supplier Tags
Physical person
Total Credit Limit Amount
Block billing for the customer
Customer Recommendations: Email to Invoice
Customer recommendations: Generate Bank slip
Customer recommendations: Number of installments
Customer Recommendations: Seller Code
NIF - Tax Identification Number
Customer is inactive
Banking Details: Bank
Bank Details: Agency
Banking Details: Current account
Banking Data: CNPJ or CPF of the holder
Banking Details: Name of the account holder
Delivery Address: CNPJ / CPF of the Receiver
Delivery Address: Company Name
Delivery Address: Public Place
Delivery Address: Number
Delivery Address: Complement
Delivery Address: Neighborhood
Delivery Address: Zip Code
Delivery Address: UF
Delivery Address: City
Delivery Address: Telephone
Created sales order
For each created sales order on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created sales order
For each created sales order on Omie ERPTrigger
Customer Code
Customer: Full name / Company name
Customer: CNPJ / CPF
Customer: Fantasy Name
Customer: DDD Telephone
Customer: Contact Phone
Customer: Contact name
Address: Public place
Address: Number
Address neighborhood
Full address
Address: State
Address: City
Address: Zip Code
Address: Country Code
Customer: DDD Telephone 2
Customer: Phone 2
Customer: DDD Fax
Customer: Fax
Customer: Email
Customer: first email
Customer: Comma separated tags
Sales order ID
Sales order number
Expected billing date
Quantity of items
Installment code / Payment terms
Number of installments
Order origin
Products: Code (comma separated)
Products: Sales order description (comma separated)
Products: Code and description (separated by hyphen and comma)
Products: Description and quantity (separated by comma)
Products: Description, price and quantity (separated by hyphen and comma)
Products: CFOP (comma separated)
Products: NCM (comma separated)
Products: merchandise amount (unit amount x quantity, separated by a comma)
Products: Description and quantity (separated by line break)
Products: Code, description and quantity (separated by line break)
Product price table codes
Total sales order amount
Departments: Codes
Departments: Description of departments
Departments: Percentage of departments
Departments: Amounts two departments
Additional Information: Contact
Additional Information: Additional Invoice Data
Additional Information: Seller Code
Additional Information: Project Code
Additional Information: Customer order number
Seller's name
Carrier ID
Type of shipping
Cost of shipping
Insurance price
Own shipping vehicle
Sales order delivery forecast
Quantity of shipping volumes
Sales order delivery tracking code
Other shipping expenses
PIS amount
PIS ST value
COFINS amount
COFINS ST amount
CSLL amount
Total amount of ICMS
Amount of ICMS ST
INSS amount
IPI amount
IR amount
ISS value
Amount of deductions
Sales observation
Amount of discounts
Amount of goods
Sales contract number
Sales order stage
Sales order moved to a specific stage
When a sales order is moved to a specific stage in the Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Sales order moved to a specific stage
When a sales order is moved to a specific stage in the Omie ERPTrigger Premium
Customer: Code
Customer Full name/Company Name
Customer: CNPJ/CPF
Customer: Trade Name
Customer: Area Code
Customer: Telephone
Customer: Name
Customer: Address - Street
Customer: Address - Number
Customer: Address - Neighborhood
Customer: Address - Complement
Customer: Address - State
Customer: Address - City
Customer: Address - CEP
Customer: Address - Country code
Customer: Area code telephone 2
Customer: Telephone 2
Customer: Area code fax
Customer: Fax
Customer: Email
Customer: Primeiro e-mail
Customer: Tags (separated by comma)
Order: ID
Order: Number
Order: Estimated billing date
Order: Quantity of items
Order: Payment terms
Order: Number of installments
Order: Origin
Products: Code (separated by comma)
Order: Description (separated by comma)
Product: Code and description (separated by hyphen and comma)
Product: Description and quantity (separated by comma)
Product: Description, price and quantity (separated by hyphen and comma)
Product: CFOP (separated by comma)
Product: NCM (separated by comma)
Product: Value (unit value x quantity, separated by comma)
Product: Description and quantity (separated by line break)
Product: Code, description, and quantity (separated by line break)
Product: Price table codes
Order: Total value
Departments: Codes
Departments: Description
Departments: Percentage
Departments: Values
Additional information: Contact
Additional information: Additional invoice data
Additional Information: Salesperson code
Additional Information: Project code
Additional Information: Order number
Order: Salesperson name
Shipping: Carrier ID
Shipping: Type
Shipping: Value
Shipping: Insurance value
Shipping: Own vehicle
Shipping: Estimated delivery date of the order
Shipping: Quantity of packages
Shipping: Tracking code of the order delivery
Shipping: Other expenses
Taxes: Valor do PIS
Taxes: PIS ST value
Taxes: COFINS value
Taxes: COFINS ST value
Taxes: CSLL value
Taxes: Total ICMS value
Taxes: ICMS ST value
Taxes: INSS value
Taxes: IPI value
Taxes: Income tax value
Taxes: ISS value
Taxes: Deductions value
Order: Sales note
Order: Discount value
Order: Goods value
Order: Sales contract number
Order: Sales order stage
Date on which the sale was moved
Time at which the sale was moved
Created payment
For each created payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created payment
For each created payment on AsaasTrigger
id
Charge creation date
Billing due date
Original billing due date
Charge amount
Net charge amount
External billing identifier
Customer ID
Customer name
Customer email
Additional customer emails
Customer company
Customer CPF or CNPJ
Customer phone
Customer's cell phone
Customer address street
Customer address number
Customer address complement
Customer address neighborhood
Customer address Zip Code
Customer address State
City of customer address
Country of customer address
Customer creation date
External customer identifier
Comma-separated customer groups.
Customer creation date formatted in 'year-month-day'
Discount amount
Days before expiration to apply discount
Type of discount
Interest percentage
Fine percentage
Form of payment
Billing status
Description of the charge
Original charge amount
Calculated amount of interest and fine that must be paid after the charge is due
Date of last invoice view
Date of last viewing of the bank slip
Charge confirmation date (Credit card only)
Bill settlement date in ASAAS
Date on which the customer paid the bank slip
Invoice in URL
Bill number
Link to the bankslip file
Charge issuance fee
Charge removed
Charge creation date formatted in 'year-month-day'
Billing due date formatted in 'year-month-day'
Original billing due date formatted in 'year-month-day'
Date of last viewing of the invoice formatted in 'year-month-day'
Date of last viewing of the bank slip formatted in 'year-month-day'
Billing confirmation date (Credit card only) formatted in 'year-month-day'
Available withdrawal date (Credit card only) formatted in 'year-month-day'
Bill settlement date in ASAAS formatted in 'year-month-day'
Date on which the customer paid the bank slip formatted in 'year-month-day'
Credit data in 'year-month-day'
Available withdrawal date (any type of charge) formatted in 'year-month-day'
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link: name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Date the withdrawal becomes available
Created subscription
For each created subscription on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created subscription
For each created subscription on AsaasTrigger
Subscription ID
Subscription creation date
Customer ID
Customer creation date
Customer name
Customer email
Customer company
Customer landline
Customer's cell phone
Address: Customer's street
Address: Customer number
Address: Customer Complement
Address: Customer neighborhood
Address: Customer Zip Code
Customer CPF/CNPJ
Customer type
Additional customer emails
Customer identifier in your system
Disable sending billing notifications?
Additional observations
Customer municipal registration
Customer state registration
Address: Customer city
Address: Customer State
Address: Customer's country
Customer creation date formatted in 'year-month-day'
Customer groups
Payment link
Subscription amount
Billing frequency
Subscription description
Form of payment
Subscription status
Subscription identifier on your system
Fine percentage
Interest percentage per month
First charge: invoice URL
Subscription creation date formatted in 'year-month-day'
Due date of the first monthly installment formatted in 'year-month-day'
First monthly payment due
Deadline for monthly payments to be due
Maximum number of monthly payments to be generated
Discount amount to be applied to the charge amount
Days before expiration to apply discount.
Type of discount
Deadline for monthly installments to be due formatted in 'year-month-day'
Invoiced Service order
For every billed service order on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Invoiced Service order
For every billed service order on Omie ERPTrigger Premium
Service Order Code
Service Order Number
Service Order Amount
Forecast Date
Seller Code
Seller's name
Number of installments
Service Order Inclusion Date
Time of inclusion of the Service Order
Additional Information: Category Code
Current Account Code
Additional Information: Contact
Additional Information: Additional Invoice Data
Additional Information: Work Code
Additional Information: ART Code
Additional Information: Project Code
Additional Information: City of Service Provision
Additional Information: Receipt Number generated
Customer Order Number
Service order observations
Departments: Codes
Departments: Description of departments
Departments: Percentage of departments
Departments: Amounts two departments
Number of Service NFS-e separated by comma
Description of Services separated by comma
Description and quantity of services separated by commas
Description and unit amount of services separated by commas
Description, unit amount and quantity of services separated by commas
Description and amount of Other Retentions for services separated by commas
Description and amount of surcharges and service fees separated by commas
Due date of installments in the format - 'installment nº: due date'. Separated by comma
Due date of installments separated by comma
Customer Code
Customer: Full name / Company name
Customer: CNPJ / CPF
Customer: Fantasy Name
Customer: Telephone (DDD)
Customer: Telephone (number)
Customer: Contact name
Address: Public place
Address: Number
Address neighborhood
Full address
Address: State
Address: City
Address: Zip Code
Address: Country Code
Customer: Telephone 2 (DDD)
Customer: Telephone 2 (number)
Customer: Fax (DDD)
Customer: Fax (number)
Customer: Email
Customer: first email
Customer: Comma separated tags
Billing Date
Billing Time
Additional Information: RPS Date
Issued invoice
For each issued invoice on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Issued invoice
For each issued invoice on Omie ERPTrigger
Customer: Customer Code
Customer: Full name / Company name
Customer: CNPJ / CPF
Customer: Fantasy Name
Customer: DDD Telephone
Customer: Contact Phone
Customer: Contact name
Customer: Address - Street
Customer: Address - Number
Customer: Address - Neighborhood
Customer: Address - Complement
Customer: Address - State
Customer: Address - City
Customer: Address - Zip Code
Customer: Address - Country Code
Customer: DDD Telephone 2
Customer: Phone 2
Customer: DDD Fax
Customer: Fax
Customer: All emails
Customer: first email
Customer: Comma separated tags
Invoice ID
Invoice issuance date
Invoice issuance date formatted in dd/mm/yyyy
Product invoice: Sales order ID
Product invoice: Sales order number
Product invoice: Estimated billing date
Product invoice: Quantity of items
Product invoice: Installment code / Payment terms
Product invoice: Number of installments
Product invoice: Origin of order
Product invoice: Products: Code (separated by comma)
Product invoice: Products: Sales order description (separated by comma)
Product invoice: Products: Code and description (separated by hyphen and comma)
Product invoice: Products: Description and quantity (separated by comma)
Product invoice: Products: Description, price and quantity (separated by hyphen and comma)
Product invoice: Products: CFOP (separated by comma)
Product invoice: Products: NCM (separated by comma)
Product invoice: Products: merchandise amount (unit amount x quantity, separated by comma)
Product invoice: Products: Description and quantity (separated by line break)
Product invoice: Products: Code, description and quantity (separated by line break)
Product invoice: Product price table codes
Product invoice: Total amount of the sales order
Product invoice: Departments: Codes
Product invoice: Departments: Description of departments
Product invoice: Departments: Percentage of departments
Product invoice: Departments: Department amounts
Product invoice: Additional Information: Contact
Product invoice: Additional Information: Additional Invoice Data
Product invoice: Additional Information: Seller Code
Product invoice: Additional Information: Project Code
Product invoice: Additional Information: Customer order number
Product invoice: Seller’s name
Product invoice: Carrier ID
Product invoice: Shipping type
Product invoice: Shipping cost
Product invoice: Insurance amount
Product invoice: Own vehicle shipping
Product invoice: Sales order delivery forecast
Product invoice: Quantity of shipping volumes
Product invoice: Sales order delivery tracking code
Product invoice: Other shipping expenses
Product invoice: PIS amount
Product invoice: PIS ST amount
Product invoice: COFINS amount
Product invoice: COFINS ST amount
Product invoice: CSLL amount
Product invoice: Total ICMS amount
Product invoice: Amount of ICMS ST
Product invoice: INSS amount
Product invoice: IPI amount
Product invoice: IR amount
Product invoice: ISS amount
Product invoice: Amount of deductions
Product invoice: Sales note
Product invoice: Amount of discounts
Product invoice: Amount of goods
Product invoice: Invoice number
Product invoice: Invoice key
Invoice product: Danfe invoice
Product invoice: Tax invoice XML
Service invoice: Service Order Code
Service invoice: Service Order Number
Service invoice: Service Order Amount
Service invoice: Expected date
Service invoice: Seller Code
Service invoice: Seller's name
Service invoice: Number of Installments
Service invoice: Service Order Inclusion Date
Service invoice: Time of inclusion of the Service Order
Service invoice: Additional Information: Category Code
Service invoice: Current Account Code
Service invoice: Additional information: Contact
Service invoice: Additional Information: Additional Invoice Data
Service invoice: Additional Information: Work Code
Service invoice: Additional Information: ART Code
Service invoice: Additional Information: Project Code
Service invoice: Additional Information: City of Service Provision
Service invoice: Additional Information: Receipt Number generated
Service invoice: Customer Order Number
Service invoice: Service order observations
Service invoice: Departments: Codes
Service invoice: Departments: Description of departments
Service invoice: Departments: Percentage of departments
Service invoice: Departments: Department amounts
Service invoice: Number of Service NFS-e separated by comma
Service invoice: Description of Services separated by comma
Service invoice: Description and quantity of services separated by commas
Service invoice: Description and unit amount of services separated by commas
Service invoice: Description, unit amount and quantity of services separated by commas
Service invoice: Description and amount of Other Retentions for services separated by commas
Service invoice: Description and amount of surcharges and service fees separated by commas
Service invoice: Due date of installments in the format - 'installment no: due date'. Separated by comma
Service invoice: Due date of installments separated by comma
Service invoice: Invoice verification code
Service invoice: Invoice number
Service invoice: Tax invoice XML
Service order created
For each service order created in Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Service order created
For each service order created in Omie ERPTrigger Premium
Service order: Code
Service order: Number
Service order: Value
Service order: Forecasted Date
Service order: Salesperson code
Service order: Salesperson name
Service order: Number of installments
Service order: Inclusion date
Service order: Inclusion time
Additional information: Category code
Additional information: Checking account
Informações Adicionais: Contato
Additional information: Additional data of the invoice
Additional information: Work code
Additional information: ART code
Additional information: Project code
Additional information: City of service provision
Additional information: Generated receipt number
Service order: Customer order number
Service order: Observations
Departments: Codes
Departments: Description
Departments: Distribution percentage
Departments: Values
Service order: NFS-e and service numbers (separated by comma)
Service: Descriptions (separated by comma)
Service: Description and quantity (separated by comma)
Service: Description and unit price (separated by comma)
Service: Description, unit price, and quantity (separated by comma)
Descrição e valor de Outras Retenções dos serviços separados por vírgula
Service: Description and value of surcharges and fees (separated by comma)
Códigos municipais dos serviços separados por vírgula
Installments: Due date (in the format 'installment number: due date', separated by comma)
Installments: Due dates (separated by commas)
Customer: Code
Customer: Name/Legal Entity Name
Customer: CNPJ/CPF
Customer: Trade name
Customer: Phone area code
Customer: Telephone
Customer: Name
Customer: Street
Customer: Address number
Customer: Neighborhood
Customer: Address complement
Customer: State
Customer: City
Customer: Zip code
Customer: Country code
Customer: Phone area code 2
Customer: Telephone 2
Customer: Fax area code
Customer: Fax
Customer: Email
Customer: First email
Customer: Tags (separated by comma)
Cliente: Website
Reversed payment
For each refunded payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Reversed payment
For each refunded payment on AsaasTrigger
id
Charge creation date
Billing due date
Original billing due date
Charge amount
Net charge amount
External billing identifier
Customer ID
Customer name
Customer email
Additional customer emails
Customer company
Customer CPF or CNPJ
Customer phone
Customer's cell phone
Customer's public address
Address number
Address complement
Neighborhood
Customer address Zip Code
Customer address state
City of customer address
Country of customer address
Customer creation date
External customer identifier
Comma-separated customer groups.
Customer creation date formatted in 'year-month-day'
Discount amount
Days before expiration to apply discount
Type of discount
Interest percentage
Fine percentage
Form of payment
Billing status
Description of the charge
Original charge amount
Calculated amount of interest and fine that must be paid after the charge is due
Date of last invoice view
Date of last viewing of the bank slip
Charge confirmation date (Credit card only)
Bill settlement date in ASAAS
Date on which the customer paid the bank slip
Invoice in URL
Bill number
Link to the bank slip file
Charge issuance fee
Charge removed
Charge creation date formatted in 'year-month-day'
Billing due date formatted in 'year-month-day'
Original billing due date formatted in 'year-month-day'
Date of last viewing of the invoice formatted in 'year-month-day'
Date of last viewing of the bank slip formatted in 'year-month-day'
Billing confirmation date (Credit card only) formatted in 'year-month-day'
Available withdrawal date (Credit card only) formatted in 'year-month-day'
Bill settlement date in ASAAS formatted in 'year-month-day'
Date on which the customer paid the bank slip formatted in 'year-month-day'
Credit data in 'year-month-day'
Available withdrawal date (any type of charge) formatted in 'year-month-day'
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link: name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Confirmed payment
For each confirmed payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Confirmed payment
For each confirmed payment on AsaasTrigger
ID
Payment date created
Payment due date
Payment original due date
Payment value
Payment net value
External payment reference
Customer ID
Customer name
Customer Email
Customer Email Additionals
Customer Company
Customer CPF/CNPJ
Customer phone
Customer mobile phone
Customer Address
Address number
Address complement
Neighborhood
Customer postal code
Customer state
Customer city
Customer country
Customer date create
External customer reference
Customer groups separated by comma.
Customer date create in 'year-month-day' format
Discount value
Discount due date limit days
Discount type
Interest value
Fine percentage
Billing type
Status
Payment description
Payment original value
Calculated interest value
Invoice last viewed date
Bank slip last viewed date
Payment confirmed date (Valid only for credit card)
Asaas payment date
Customer payment date
Invoice URL
Invoice number
Link to the bank slip file
Payment creation fee
Payment deleted
Payment date created in 'year-month-day' format
Payment due date in 'year-month-day' format
Payment original due date in 'year-month-day' format
Invoice last viewed date in 'year-month-day' format
Bank slip last viewed date in 'year-month-day' format
Payment confirmed date (Valid only for credit card) in 'year-month-day' format
Withdrawal available at (Valid only for credit card) in 'year-month-day' format
Asaas payment date in 'year-month-day' format
Customer payment date in 'year-month-day' format
Credit data in 'year-month-day'
Withdrawal available at (any billing type) in 'year-month-day' format
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Withdrawal available at (Valid only for credit card)
Invoiced Sales order
For every billed sales order on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Invoiced Sales order
For every billed sales order on Omie ERPTrigger Premium
Customer Code
Customer: Full name / Company name
Customer: CNPJ / CPF
Customer: Fantasy Name
Customer: Telephone (DDD)
Customer: Telephone (number)
Customer: Contact name
Address: Public place
Address: Number
Address neighborhood
Full address
Address: State
Address: City
Address: Zip Code
Address: Country Code
Customer: Telephone 2 (DDD)
Customer: Telephone 2 (number)
Customer: Fax (DDD)
Customer: Fax (number)
Customer: Email
Customer: first email
Customer: Comma separated tags
Sales order ID
Sales order number
Expected billing date
Quantity of items
Installment code / Payment terms
Number of installments
Order origin
Products: Code (comma separated)
Products: Sales order description (comma separated)
Products: Code and description (separated by hyphen and comma)
Products: Description and quantity (separated by comma)
Products: Description, price and quantity (separated by hyphen and comma)
Products: CFOP (comma separated)
Products: NCM (comma separated)
Products: merchandise amount (unit amount x quantity, separated by a comma)
Products: Description and quantity (separated by line break)
Products: Code, description and quantity (separated by line break)
Product price table codes (separated by comma)
Total sales order amount
Departments: Codes
Departments: Description of departments
Departments: Percentage of departments
Departments: Amounts two departments
Additional Information: Contact
Additional Information: Additional Invoice Data
Additional Information: Seller Code
Additional Information: Project Code
Additional Information: Customer order number
Seller's name
Carrier ID
Type of shipping
Cost of shipping
Insurance price
Own shipping vehicle
Sales order delivery forecast
Quantity of shipping volumes
Sales order delivery tracking code
Other shipping expenses
PIS amount
PIS ST value
COFINS amount
COFINS ST amount
CSLL amount
Total amount of ICMS
Amount of ICMS ST
INSS amount
IPI amount
IR amount
ISS value
Amount of deductions
Sales observation
Amount of discounts
Amount of goods
Sales contract number
Sales order stage
Billing date
Billing time
NFS-e number of the order separated by a comma
Accounts payable created
For each accounts payable created in Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Accounts payable created
For each accounts payable created in Omie ERPTrigger
Customer: Code
Customer: Full Name/Legal Name
Customer: CNPJ/CPF
Customer: Trading Name
Customer: DDD Telephone
Customer: Telephone
Customer: Contact name
Customer: Address - Street
Customer: Address - Number
Customer: Address - Neighborhood
Customer: Address - Additional Information
Customer: Address - State
Customer: Address - City
Customer: Address - CEP
Cliente: Address - Country code
Customer: DDD Telephone 2
Customer: Telephone 2
Customer: DDD Fax
Customer: Fax
Customer: Email
Customer: First email
Customer: Tags (separated by comma)
Accounts payable: Category code
Accounts payable: Integration code
Accounts payable: ID
Accounts payable: Issuance date
Accounts payable: Payment due date
Accounts payable: Due date
ID da conta corrente
Accounts payable: Document number
Accounts payable: Fiscal document number
Accounts payable: Installment number
Accounts payable: Order number
Observations
Accounts payable: COFINS withholding
Accounts payable: CSLL withholding
Accounts payable: IR withholding
Accounts payable: ISS withholding
Accounts payable: PIS withholding
Accounts payable: Payment status
Accounts payable: COFINS value
Accounts payable: CSLL value
Accounts payable: Amount
Accounts payable: INSS amount
Accounts payable: IR amount
Accounts payable: ISS amount
Accounts payable: PIS amount
Departments: ID (separated by comma)
Departments: Descriptions (separated by comma)
Departments: Division percentages (separated by comma)
Departments: Values (separated by comma)
Accounts payable: Total tax amount
Accounts receivable created
When an accounts receivable is created in Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Accounts receivable created
When an accounts receivable is created in Omie ERPTrigger
Accounts Receivable: ID
Accounts Receivable: Integration-generated posting code
Contact: Customer/Supplier Code
Contact: Code provided by the integrator
Accounts receivable: Posting amount
Accounts receivable: Category code
Accounts receivable: Current account ID
Accounts receivable: Document number
Accounts receivable: Installment number
Accounts receivable: Document type code
Accounts receivable: Fiscal document number
Accounts receivable: Order number
Accounts receivable: NFE access key
Accounts receivable: Clearance note
Accounts receivable: Compensation slip barcode
Accounts receivable: Check CMC7 code
Data de emissão
Data de emissão (aaaa-mm-dd)
Data de registro
Data de registro (aaaa-mm-dd)
Accounts receivable: Forecast date
Data de previsão (aaaa-mm-dd)
Data de vencimento
Data de vencimento (aaaa-mm-dd)
Accounts receivable: Origin code
Accounts receivable: PIS Value
Accounts receivable: PIS withholding
Accounts receivable: COFINS value
Accounts receivable: COFINS withholding
Accounts receivable: CSLL value
Accounts receivable: CSLL withholding
Accounts receivable: Income tax value
Accounts receivable: Income tax withholding
Accounts receivable: ISS value
Accounts receivable: ISS withholding
Accounts receivable: Posting block (S/N)
Accounts receivable: Status
Accounts receivable: INSS value
Accounts receivable: Salesperson code
Contact: Customer code
Contact: Name/Legal Name
Contact: CNPJ/CPF
Contact: Trade name
Contact: Phone area code
Contact: Telephone
Contact: Name
Address: Street
Address: Number
Address: Neighborhood
Address: Complement
Address: State
Address: City
Address: ZIP Code
Address: Country code
Contact: Telephone code 2
Contact: Phone number 2
Contact: Fax area code
Contact: Fax
Contact: Email
Contact: Primary email
Contact: Tags (comma-separated)
Overdue payment
For each overdue payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Overdue payment
For each overdue payment on AsaasTrigger
Billing ID
Charge creation date
Billing due date
Original billing due date
Charge amount
Net charge amount
External billing identifier
Customer ID
Customer name
Customer email
Additional customer emails
Customer company
Customer CPF or CNPJ
Customer phone
Customer's cell phone
Customer's public address
Address number
Address complement
Neighborhood
Customer address Zip Code
Customer address State
City of customer address
Country of customer address
Customer creation date
External customer identifier
Comma-separated customer groups.
Customer creation date formatted in 'year-month-day'
Discount amount
Days before expiration to apply discount
Type of discount
Interest percentage
Fine percentage
Form of payment
Status
Description of the charge
Original charge amount
Calculated amount of interest and fine that must be paid after the charge is due
Date of last viewing of the invoice
Date of last viewing of the bank slip
Charge confirmation date (Credit card only)
Bill settlement date in ASAAS
Date on which the customer paid the bank slip
Invoice in URL
Bill number
Link to the bank slip file
Charge issuance fee
Charge removed
Charge creation date formatted in 'year-month-day'
Billing due date formatted in 'year-month-day'
Original billing due date formatted in 'year-month-day'
Date of last viewing of the invoice formatted in 'year-month-day'
Date of last viewing of the bank slip formatted in 'year-month-day'
Billing confirmation date (Credit card only) formatted in 'year-month-day'
Available withdrawal date (Credit card only) formatted in 'year-month-day'
Bill settlement date in ASAAS formatted in 'year-month-day'
Date on which the customer paid the bank slip formatted in 'year-month-day'
Credit data in 'year-month-day'
Available withdrawal date (any type of charge) formatted in 'year-month-day'
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link: name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Cobrança recebida
For each received payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Cobrança recebida
For each received payment on AsaasTrigger
ID
Payment date created
Payment due date
Payment original due date
Payment value
Payment net value
External payment reference
Customer ID
Customer name
Customer Email
Customer Email Additionals
Customer Company
Customer CPF/CNPJ
Customer phone
Customer mobile phone
Customer Address
Address number
Address complement
Neighborhood
Customer postal code
Customer state
Customer city
Customer country
Customer date create
External customer reference
Customer groups separated by comma.
Customer date create in 'year-month-day' format
Discount value
Discount due date limit days
Discount type
Interest value
Fine percentage
Billing type
Status
Payment description
Payment original value
Calculated interest value
Invoice last viewed date
Bank slip last viewed date
Payment confirmed date (Valid only for credit card)
Asaas payment date
Customer payment date
Invoice URL
Invoice number
Link to the bank slip file
Payment creation fee
Payment deleted
Payment date created in 'year-month-day' format
Payment due date in 'year-month-day' format
Payment original due date in 'year-month-day' format
Invoice last viewed date in 'year-month-day' format
Bank slip last viewed date in 'year-month-day' format
Payment confirmed date (Valid only for credit card) in 'year-month-day' format
Withdrawal available at (Valid only for credit card) in 'year-month-day' format
Asaas payment date in 'year-month-day' format
Customer payment date in 'year-month-day' format
Credit data in 'year-month-day'
Withdrawal available at (any billing type) in 'year-month-day' format
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link: name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Withdrawal available at
Create or update customer
create or update a customer on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create or update customer
create or update a customer on Omie ERPAction
Update customer data
Update customer based on
Full name / Company name Required
CNPJ / CPF
Customer Type
Telephone (DDD)
Telephone number)
Telephone 2 (DDD)
Telephone 2 (number)
Contact name
Trade name / Short name Required
Address format
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Country
Address: UF
Address: City
Address: Zip Code
Telephone 2 (DDD)
Telephone 2 (number)
Fax (DDD)
Fax (number)
Web site
State registration
Municipal registration
Suframa Registration
Applicant for Simples Nacional
Type of Activity
Rural producer
Taxpayer
Internal Observation
Detailed Observation
Tags
Total Credit Limit Amount
Delivery Address: CNPJ / CPF of the Receiver
Delivery Address: Company Name
Delivery Address: Public Place
Delivery Address: Number
Delivery Address: Complement
Delivery Address: Neighborhood
Delivery cost: Zip Code
Delivery Address: UF
Delivery Address: City
Delivery Address: Telephone
Recommendations: Email for invoice
Customer Bank Code
Customer Bank Branch
Customer Bank Checking Account
Document of the Customer's Bank Account Holder (CPF/CNPJ)
Name of Customer's Bank Account Holder
Default Salesperson selection
Default salesperson
Customer: Send attachments by e-mail
Salesperson: Email
Create service order
create a service order on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create service order
create a service order on Omie ERPAction
Update customer data
Update customer based on
Customer: Full name or Company name Required
Customer: Trade name / Short name Required
Customer: CNPJ / CPF
Sales forecast Required
Stage
Service: Brief description Required
Service: Quantity Required
Service: Unit amount Required
Bank account selection mode
Additional information: Current Account
Bank account name
Categoria selection mode
Additional information: Category
Category
Create category as a sub-category of:
Category notes
P&L account
Additional information: UF Service Provision Required
Additional information: City Service Provision Required
Installment period
Number of installments
Gap between installments
Department selection mode
Department
Departamento
Create department as a sub-department of:
Service: Service Code
Seller selection
Seller
Seller: Email
Customer: Telephone (DDD)
Customer: Telephone (number)
Customer: Phone 2 area code
Customer: Phone Number 2
Customer: Email
Customer: Contact name
Customer: Internal Observation
Customer: Detailed Observation
Address format
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Country
Address: UF
Address: City
Address: Zip Code
Inscrição Estadual
Inscrição Municipal
Customer Bank Code
Customer Bank Branch
Customer Bank Checking Account
Document of the Customer's Bank Account Holder (CPF/CNPJ)
Name of Customer's Bank Account Holder
Customer: Tags
Customer: Send attachments by e-mail
Service: Discount Type
Service: Discount Amount
Service: ISS Tax Rate
Service: Withholding at source
Service: Generate account receivable for this item?
Additional information: Customer order number
Additional information: Sales contract number
Additional information: Contact
Project selection mode
Additional information: Project
Project
Additional information: Additional data for the Invoice
Additional information: Work code
Additional information: ART Code
Additional information: RPS date
Email to send the bank slip, receipt, NF-e
Email to customer: Send bank slip
Email to the customer: Send the NFS-e link generated at the city hall
Email to the customer: Send a service receipt (instead of NFS-e)
Sales notes (not displayed on the invoice)
Create purchase order
create purchase order on Omie ERPHow it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Create purchase order
create purchase order on Omie ERPAction
Update client
Client: Full name or legal entity name Required
Client: Trade name/Abbreviated name Required
Client: State Required
Client: CNPJ/CPF
Product: Description Required
Product: Quantity Required
Product: Unit price Required
Product: Code
Product: Discount amount
Purchase: Revenue forecast Required
Purchase: Number of installments
Client: Phone area code
Client: Phone number
Client: Secondary phone area code
Client: Secondary phone
Client: Email
Client: State registration number
Client: Contact name
Client: Internal note
Client: Detailed note
Address format
Address: Street
Address: Number
Address: Additional information
Address: Neighborhood
Address: Country
Address: City
Address: Zipcode
Delivery address: CNPJ/CPF
Delivery address: Legal entity name
Delivery address: Street
Delivery address: Number
Delivery address: Additional information
Delivery address: Neighborhood
Delivery address: ZIP code
Delivery address: State
Delivery address: City
Delivery address: Phone
Client: Tags
Client: Total credit limit value
Client: Bank code
Client: Bank branch
Client: Checking account number
Client: CPF/CNPJ of the bank account holder
Client: Name of the bank account holder
Shipping: Carrier code
Shipping: Carrier integration code
Shipping: Type
Shipping: Vehicle license plate
Shipping: Vehicle state
Shipping: Number of packages
Shipping: Kind of volumes
Shipping: Brand of volumes
Shipping: Numbering of volumes
Shipping: Cost
Shipping: Insurance value
Shipping: Seal number
Shipping: Other incidental expenses
Purchase: Payment destination department
Schedule/issue invoice
Schedule/issue an invoice on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Schedule/issue invoice
Schedule/issue an invoice on AsaasAction Premium
Customer: Name Required
Customer: CPF/CNPJ Required
Invoice: Amount Required
Authorize invoice immediately Required
Invoice: Date of issue
Address: Street Name
Address: Number
Endereço: Zip Code
Invoice: Description of services
Customer: E-mail
Customer: Telephone
Customer: Mobile phone
Customer: Company
Invoice: Deductions Required
Invoice: Name of municipal service
Invoice: Municipal Service Code
Invoice: Should the service recipient withhold ISS? Required
Invoice: ISS Tax Rate Required
Invoice: COFINS Tax rate Required
Invoice: CSLL Tax rate Required
Invoice: INSS Tax rate Required
Invoice: IR Tax rate Required
Invoice: PIS Tax rate Required
Invoice: External reference
Invoice: Notes
Address: Additional Information
Address: Neighborhood
Customer: Customer identifier in your system
Customer: Disable billing notification sending?
Customer: Additional e-mails
Customer: Municipal registration
Customer: State registration
Customer: Observations
Customer: Group's name
Should email be used to find the customer?
Create account payable
create an account payable on Omie ERPHow it works:
Whenever something happens on the source app
1. An accounts payable will be created/updated on Omie ERP
2. A contact associated with the accounts payable will be created/updated on Omie ERP
All happening in a single automation! ✨
Create account payable
create an account payable on Omie ERPAction
Update customer data
Update customer based on
Payee/Supplier: CNPJ / CPF
Payee/Supplier: Full name or Company name Required
Payee/Supplier: Trade name / Short name Required
Due date Required
Account amount Required
Category selection mode
Category
Category
Create category as a sub-category of:
Category notes
P&L account
Payment forecast
Bank account selection mode
Current account
Bank account name
Automatically mark document as paid
Payee/Supplier: Telephone area code
Payee/Supplier: Telephone Number
Favorecido/Fornecedor: DDD do Telefone 2
Favorecido/Fornecedor: Número do Telefone 2
Payee/Supplier: Email
Payee/Supplier: Contact name
Cliente: Observação Interna
Cliente: Observação Detalhada
Address format
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Country
Address: UF
Address: City
Address: Zip Code
Favorecido/Fornecedor: Tags
Customer Bank Code
Customer Bank Branch
Customer Bank Checking Account
Document of the Customer's Bank Account Holder (CPF/CNPJ)
Name of Customer's Bank Account Holder
Customer: Send attachments by e-mail
Details: Invoice
Details: Issue date
Details: Registration date
Seleção de informações de Integração Bancária e CNAB
Payment method
Payment method
Boleto bar code
Interest rate
Fine
Purpose of the transfer
Purpose of the transfer
Pix key or QR Code
Bank code
Bank agency number
Bank account number
Account holder's CPF/CNPJ
Account holder's name
Project selection mode
Details: Project
Project
Details: Observations
Department selection mode
Department
Departamento
Create department as a sub-department of:
Withheld taxes: PIS amount
Taxes withheld: Withhold the PIS Amount
Taxes withheld: CSLL Amount
Taxes withheld: Withhold the CSLL Amount
Taxes withheld: ISS Amount
Taxes withheld: Withhold the ISS Amount
Withheld taxes: COFINS amount
Taxes withheld: Withhold the COFINS Amount
Taxes withheld: IR Amount
Taxes withheld: Withhold the IR Amount
Taxes withheld: INSS Amount
Taxes withheld: Withhold the INSS Amount
Miscellaneous: Order number
Miscellaneous: Document type
Miscellaneous: Document number
Miscellaneous: NF-e Key
Miscellaneous: Barcode
Miscellaneous: Salesperson
Create sales order (single item)
create a sales order on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create sales order (single item)
create a sales order on Omie ERPAction Premium
Update customer data
Update customer based on
Customer: Full name or Company name Required
Customer: Trade name / Short name Required
Address: UF Required
Customer: CNPJ / CPF
Sales forecast Required
Stage
Product: Description Required
Product: Quantity Required
Product: Unit amount Required
Product: Code
Bank account selection mode
Additional information: Current Account
Bank account name
Additional information: Category Required
Installment period
Number of installments
Gap between installments
Installments: Document type
Installments: Payment method
Tax Scenario
Customer: Telephone (DDD)
Customer: Telephone (number)
Customer: Phone 2 area code
Customer: Phone Number 2
Customer: Email
State registration
Customer: Contact name
Customer: Internal Observation
Customer: Detailed Observation
Address format
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Country
Address: City
Address: Zip Code
Delivery Address: CNPJ / CPF of the Receiver
Delivery Address: Company Name
Delivery Address: Public Place
Delivery Address: Number
Delivery Address: Complement
Delivery Address: Neighborhood
Delivery Address: Zip Code
Delivery Address: UF
Delivery Address: City
Delivery Address: Telephone
Customer: Tags
Total Credit Limit Amount
Customer Bank Code
Customer Bank Branch
Customer Bank Checking Account
Document of the Customer's Bank Account Holder (CPF/CNPJ)
Name of Customer's Bank Account Holder
Customer: Send attachments by e-mail
Product: Discount Type
Product: Discount Amount
Product: Generate account receivable for the sale proceeds?
Shipping: Corporate Name Carrier
Shipping: Carrier's CNPJ
Shipping: Shipping type
Shipping: Vehicle plate
Shipping: UF of the vehicle
Shipping: RNTRC (ANTT)
Shipping: Number of volumes
Shipping: Type of volumes
Shipping: Brand of volumes
Shipping: Volume numbering
Shipping: Net weight
Shipping: Gross weight (kg)
Shipping: Shipping cost
Shipping: Insurance amount
Shipping: Seal number
Shipping: Other incidental expenses
Shipping: Delivery forecast
Shipping: Tracking code
Shipping: Transport carried out by own vehicle
Seller selection
Seller
Seller: Email
Additional information: Customer order number
Additional information: Sales contract number
Additional information: Contact
Additional information: Project
Additional information: Additional data for the Invoice
Additional information: Invoice for Final Consumption
Additional information: Email to send the bank slip, DANFE and NF-e XML
Send bank slip, DANFE and NF-e
Operation Presence Indicator.
Intermediary Indicator.
CNPJ of the Intermediary.
Identification at the Intermediary.
The customer is foreign, but in fact it is not an export
Boarding location (or border crossing)
State of Boarding Location
Dispatch Location
Sales notes (not displayed on the invoice)
Fuel Product: ANP Product Code
Fuel Product: Product Description according to ANP
Fuel Product: CODIF Registration
Fuel Product: % of LPG Derived from Petroleum
Fuel Product: % of National Natural Gas
Fuel Product: % of Imported Natural Gas
Fuel Product: Starting Amount
Fuel Product: Quantity Billed at Ambient Temperature
Fuel Product: Consumption UF
Fuel Product: CIDE Calculation Base (in quantity)
Fuel Product: Aliq Amount. in Reais from CIDE
Fuel Product: CIDE Amount
Fuel Product: Calculation Base of the Sender UF (ICMS Transfer)
Fuel Product: Amount of the Sender UF (ICMS Transfer)
Fuel Product: Calculation Base of the UF Destination (ICMS Transfer)
Fuel Product: Amount of Destination UF (ICMS Transfer)
Department
Generate billing
generate a billing on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Generate billing
generate a billing on AsaasAction
Customer: take email into account as a uniqueness criterion?
Customer: Name Required
Customer: CPF/CNPJ Required
Billing: Amount Required
Billing: Due date Required
Billing: Description
Customer: Email
Customer: Landline
Customer: Cell phone
Customer: Company
Split payment
Split: Types of subaccounts for payment splittingAccount selection method
Split: Number of subaccount(s) or Wallet IDs
[Split 1] Select subaccount
[Split 1] Wallet ID
[Split 1] Value type
[Split 1] Value
[Split 2] Select subaccount
[Split 2] Wallet ID
[Split 2] Value type
[Split 2] Value
[Split 3] Select subaccount
[Split 3] Wallet ID
[Split 3] Value type
[Split 3] Value
[Split 4] Select subaccount
[Split 4] Wallet ID
[Split 4] Value type
[Split 4] Value
[Split 5] Select subaccount
[Split 5] Wallet ID
[Split 5] Value type
[Split 5] Value
[Split 6] Select subaccount
[Split 6] Wallet ID
[Split 6] Value type
[Split 6] Value
[Split 7] Select subaccount
[Split 7] Wallet ID
[Split 7] Value type
[Split 7] Value
[Split 8] Select subaccount
[Split 8] Wallet ID
[Split 8] Value type
[Split 8] Value
[Split 9] Select subaccount
[Split 9] Wallet ID
[Split 9] Value type
[Split 9] Value
[Split 10] Select subaccount
[Split 10] Wallet ID
[Split 10] Value type
[Split 10] Value
Billing: Payment method
Billing: External reference
Billing: Number of installments
Billing: Discount amount
Billing: Days before due date to apply discount
Billing: Type of discount
Billing: Percentage of interest per month
Billing: Type of fine
Billing: Fine
Billing: Send via post?
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Zip Code
Customer: Customer identifier in your system
Customer: Disable sending billing notifications?
Cliente: Canais de notificações a serem habilitados
Customers: Notifications to enable
Cliente: Dias antes do vencimento para enviar a notificação
Cliente: Dias após o vencimento para enviar a notificação
Customer: Additional emails
Customer: Municipal registration
Customer: State registration
Customer: Observations
Customer: Group name
Create account receivable
create an account receivable on Omie ERPHow it works:
Whenever something happens on the source app
1. An accounts receivable will be created/updated on Omie ERP
2. A contact associated with the accounts receivable will be created/updated on Omie ERP
All happening in a single automation! ✨
Create account receivable
create an account receivable on Omie ERPAction
Update customer data
Update customer based on
Customer: CNPJ / CPF
Customer: Full name or Company name Required
Customer: Trade name / Short name Required
Due date Required
Account amount Required
Download document automatically
Data do recebimento recebimento
Account discount
Account interest
Account fines
Category selection mode
Category
Category
Create category as a sub-category of:
Category notes
P&L account
Receipt forecast
Bank account selection mode
Checking account
Bank account name
Customer: Telephone (DDD)
Customer: Telephone (number)
Customer: Phone 2 area code
Customer: Phone Number 2
Customer: Email
Customer: Contact name
Customer: Internal Observation
Customer: Detailed Observation
Address format
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Country
Address: UF
Address: City
Address: Zip Code
Customer Bank Code
Customer Bank Branch
Customer Bank Checking Account
Document of the Customer's Bank Account Holder (CPF/CNPJ)
Name of Customer's Bank Account Holder
Customer: Tags
Customer: Send attachments by e-mail
Details: Invoice
Details: Issue date
Project selection mode
Details: Project
Project
Details: Seller
Details: Observations
Department selection mode
Department
Departamento
Create department as a sub-department of:
Repeat bill as installments
Day of the month to create installments
Day of the week to create installments
Days between installments
Number of installments
Withheld taxes: PIS amount
Taxes withheld: Withhold the PIS Amount
Taxes withheld: CSLL Amount
Taxes withheld: Withhold the CSLL Amount
Taxes withheld: ISS Amount
Taxes withheld: Withhold the ISS Amount
Withheld taxes: COFINS amount
Taxes withheld: Withhold the COFINS Amount
Taxes withheld: IR Amount
Taxes withheld: Withhold the IR Amount
Taxes withheld: INSS Amount
Taxes withheld: Withhold the INSS Amount
Miscellaneous: Order number
Miscellaneous: Document type
Miscellaneous: Document number
Miscellaneous: NSU/TID
Miscellaneous: Barcode
Miscellaneous: Registration date
Miscellaneous: NF-e Key
Create contract (single item)
create a new contract on Omie ERPHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create contract (single item)
create a new contract on Omie ERPAction Premium
Update customer data
Update customer based on
Customer: Full name or Company name Required
Customer: Trade name / Short name Required
Customer: CNPJ / CPF
Auto generate contract number?
Contract: Contract number
Contract: Initial term of the services contract Required
Contract: Final term of the service contract Required
Contract: Contract billing type
Contract: Billing day Required
Situação do contrato
Service: Service Code
Service: Full description of the service provided Required
Service: Number of services Required
Service: Unit amount of the service Required
Service: Discount type
Service: Discount amount
Withhold ISS?
Additional information: Category Required
Additional information: City of Service Provision Required
Additional information: UF of Service Provision Required
Department selection mode
Departamento
Departamento
Create department as a sub-department of:
Additional information: Work code
Additional information: ART Code
Additional information: Project
Additional information: Current Account Required
Additional information: Contact Name
Email to customer: Email addresses Required
Due date and NFS-e Texts: Due date type Required
Due date and NFS-e Texts: Number of days to maturity
Due date and NFS-e Texts: Fixed due date
Additional information: Selection of sellers
Additional information: Seller
Seller: Email
Due date and NFS-e Texts: Will due date only occur in the following month?
Due date and NFS-e Texts: Anticipate or postpone Saturdays, Sundays and holidays?
Due date and NFS-e Texts: Add 'Contract Number' to the description of services in NFS-e
NFS-e due date and Texts: Add the installment due date to the description of services in the NFS-e?
Due date and NFS-e Texts: Reference period
Due date and NFS-e Texts: Add the reference period associated with billing?
Starting day of the billing period
End day of the billing period
Send a service receipt (instead of NFS-e)
Email to the customer: Send the NFS-e link generated at City Hall?
Notes: Contract notes
Notes: Additional data for the Invoice
Email to the customer: Send the bank slip(s) or PIX(es) of billing?
Billing and Forecasts: Generate account receivable for this item?
Customer: Telephone area code
Customer: Phone Number
Customer: Phone 2 area code
Customer: Phone Number 2
Customer: Email
Customer: Contact name
Customer: Internal Observation
Customer: Detailed Observation
Address format
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Country
Address: UF
Address: City
Address: Zip Code
Customer Bank Code
Customer Bank Branch
Customer Bank Checking Account
Document of the Customer's Bank Account Holder (CPF/CNPJ)
Name of Customer's Bank Account Holder
Customer: Tags
Customer: Send attachments by e-mail
Create a subscription
create a subscription on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create a subscription
create a subscription on AsaasAction
Customer: take email into account as a uniqueness criterion?
Customer: Name Required
Customer: CPF/CNPJ Required
Subscription: Amount Required
Subscription: Due date of the first monthly payment Required
Subscription: Frequency Required
Signature: Description
Customer: Email
Customer: Landline
Customer: Cell phone
Customer: Company
Subscription: Payment method
Subscription: Discount amount
Subscription: Days before due date to apply discount
Subscription: Discount type
Subscription: Interest percentage per month
Signature: Type of fine
Signature: Fine
Subscription: Deadline for monthly installments to be due
Subscription: Maximum number of monthly payments
Signature: Identifier on your system
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Zip Code
Customer: Customer identifier in your system
Customer: Disable sending billing notifications?
Cliente: Canais de notificações a serem habilitados
Customers: Notifications to enable
Cliente: Dias antes do vencimento para enviar a notificação
Cliente: Dias após o vencimento para enviar a notificação
Customer: Additional emails
Customer: Municipal registration
Customer: State registration
Customer: Observations
Customer: Group name
Split payment
Split: Types of subaccounts for payment splittingAccount selection method
Split: Number of subaccount(s) or Wallet IDs
[Split 1] Select subaccount
[Split 1] Wallet ID
[Split 1] Value type
[Split 1] Value
[Split 2] Select subaccount
[Split 2] Wallet ID
[Split 2] Value type
[Split 2] Value
[Split 3] Select subaccount
[Split 3] Wallet ID
[Split 3] Value type
[Split 3] Value
[Split 4] Select subaccount
[Split 4] Wallet ID
[Split 4] Value type
[Split 4] Value
[Split 5] Select subaccount
[Split 5] Wallet ID
[Split 5] Value type
[Split 5] Value
[Split 6] Select subaccount
[Split 6] Wallet ID
[Split 6] Value type
[Split 6] Value
[Split 7] Select subaccount
[Split 7] Wallet ID
[Split 7] Value type
[Split 7] Value
[Split 8] Select subaccount
[Split 8] Wallet ID
[Split 8] Value type
[Split 8] Value
[Split 9] Select subaccount
[Split 9] Wallet ID
[Split 9] Value type
[Split 9] Value
[Split 10] Select subaccount
[Split 10] Wallet ID
[Split 10] Value type
[Split 10] Value
Didn't find your use case? Send suggestion.
Automate Omie ERP and Asaas with Pluga integrations
Explore automation templates
For each received payment on Asaas, create an account receivable on Omie ERP
EXPLORE For each received payment on Asaas, create an account payable on Omie ERP
EXPLORE For each received payment on Asaas, create or update a customer on Omie ERP
EXPLORE For each received payment on Asaas, create a sales order on Omie ERP
EXPLORE For each received payment on Asaas, create a service order on Omie ERP
EXPLORE For each created payment on Asaas, create a service order on Omie ERP
EXPLORE For each created payment on Asaas, create an account receivable on Omie ERP
EXPLORE For every billed service order on Omie ERP, generate a billing on Asaas
EXPLORE For every billed sales order on Omie ERP, generate a billing on Asaas
EXPLORE For each created sales order on Omie ERP, generate a billing on Asaas
EXPLORE For each created payment on Asaas, create a new contract on Omie
EXPLORE For each received payment on Asaas, create a new contract on Omie
EXPLORE For each created sales order on Omie ERP, create or update a customer on Asaas
EXPLORE When a customer/supplier is created on Omie ERP, create or update a customer on Asaas
EXPLORE For every billed service order on Omie ERP, create a subscription on Asaas
EXPLORE For every billed sales order on Omie ERP, create a subscription on Asaas
EXPLORE For each created sales order on Omie ERP, create a subscription on Asaas
EXPLORE For each created subscription on Asaas, create a service order on Omie ERP
EXPLORE For each created subscription on Asaas, create an account receivable on Omie ERP
EXPLORE For each created subscription on Asaas, create a new contract on Omie
EXPLORE For each issued invoice on Omie ERP, generate a billing on Asaas
EXPLORE For each issued invoice on Omie ERP, create a subscription on Asaas
EXPLORE For each created subscription on Asaas, create a sales order on Omie ERP
EXPLORE For each confirmed payment on Asaas, create an account receivable on Omie ERP
EXPLORE For each confirmed payment on Asaas, create an account payable on Omie ERP
EXPLORE For each confirmed payment on Asaas, create or update a customer on Omie ERP
EXPLORE For each confirmed payment on Asaas, create a sales order on Omie ERP
EXPLORE For each confirmed payment on Asaas, create a service order on Omie ERP
EXPLORE For each confirmed payment on Asaas, create a new contract on Omie
EXPLORE For each created payment on Asaas, create an account payable on Omie ERP
EXPLORE When a sales order is moved to a specific stage in the Omie ERP, generate a billing on Asaas
EXPLORE When a sales order is moved to a specific stage in the Omie ERP, create or update a customer on Asaas
EXPLORE When a sales order is moved to a specific stage in the Omie ERP, create a subscription on Asaas
EXPLORE For each service order created in OmieERP, generate a billing on Asaas
EXPLORE For each service order created in OmieERP, create a subscription on Asaas
EXPLORE When an accounts receivable is created in OmieERP, generate a billing on Asaas
EXPLORE When an accounts receivable is created in OmieERP, create a subscription on Asaas
EXPLORE For each created payment on Asaas, create purchase order on Omie ERP
EXPLORE For each received payment on Asaas, create purchase order on Omie ERP
EXPLORE For each created subscription on Asaas, create purchase order on Omie ERP
EXPLORE For each confirmed payment on Asaas, create purchase order on Omie ERP
EXPLORE For each service order created in Omie ERP, create or update a customer on Asaas
EXPLORE Miss an automation with this apps?
Say to us!Trusted by over 10.000 amazing companies
How to integrate apps with Pluga?
Pluga allows you to integrate two or more apps in a simple, practical way without needing to type a single line of code. Here are the steps to automate your tasks and start focusing on what really matters.
-
What is the automation trigger?
The trigger is the step that initiates automation. In the integration process, it is selected after choosing the source app. For example, if you choose Facebook Lead Ads as the source app, the trigger could be: For each response on an advertisement.
-
What is an action within an automation?
The action serves as a response to the previously selected trigger. That is, it occurs once the trigger is activated. For example, in an automation between Facebook Lead Ads (source) and Google Sheets (destination), as soon as the trigger “For each response on an advertisement” is activated in the source app, the action “Add data to a new row on a spreadsheet” will be carried out in the destination app.
-
How does information mapping work?
Information mapping is where you configure which captured information from the source app will be sent to each field in the destination app(s).
For example, in an automation between Facebook Lead Ads and Google Sheets, this step is where you will determine which contact information should fill in the spreadsheet fields.
-
Is it possible to have more than one action?
With Pluga, you can create automations by integrating several apps at once. For example, you can integrate Facebook Lead Ads + Google Sheets + Slack, so when the trigger is activated, the first action is executed and a notification is sent via Slack.
Automate Omie ERP + Asaas
and say goodbye to manual (and tedious) tasks!
By connecting the apps you use through Pluga, you can automate various processes in your routine and have time for tasks that really matter. 
Omie ERP
ERPOmie ERP is a business management system that integrates various areas such as sales, purchasing, financial, inventory, and accounting, facilitating the administration and control of a company.
Integrations with Omie ERP Visit Omie ERP Asaas
PaymentAsaas is a financial management platform designed to simplify and reduce business bureaucracy. Its features include providing payment methods, handling various types of sales, and managing cash flow.
Integrations with Asaas Visit Asaas